What are the scenarios in which the ALM sync between Standard and Deployed mode will break

sruthee

AjayM

The most obvious scenario is when production model is taken out of deployed mode, and then a structural change is made within the prod model (renaming module/lineitem/list, changing formula, changing non-production list items, changing action mapping, modifying user access, taking a backup copy of the model, adding a revision tag etc).

sahilkumbhare

The connection between the development (Dev) and production (Prod) environments in Anaplan can break in a variety of situations, including the following:

1 Inconsistent standards :- If the development environment and the production environment use different standards, this can lead to differences in functionality and data. 

2 Changes in Dependencies :- Changes to modules or events in Dev that are not published in Prod can create dependency issues that cause the connection to break. 

3 Incorrect export process :- Errors in the export process (such as missing elements or incorrect settings) can break the connection between the environments. 

4 Data Synchronization Issues :- If data updates or changes in Dev are not well synchronized with Prod, this can lead to conflicts and connections. 

5 User Access and Permission Changes :- Changing user roles or permissions in one environment without reflecting the changes in  other environments will prevent proper access and functionality. 

6 Business Logic Changes :- If business rules or calculations are changed in Dev but not in Prod, this will cause a difference between the product and the process operation. 

7 Script or Formula Errors :- Errors in formulas or scripts that exist in Dev but are not fixed or tested before being moved to Prod can break functionality. 

8 Configuration Changes :- Any configuration changes made in development that are not replicated in production will cause a difference in how the model works. Process control, quality testing, and clear data.