About Synchronizing Configuration Changes
When you modify configuration settings in Max, you may need to manually synchronize for your changes to take effect. When data model changes are involved, such as for new field or object definitions, updates are not deployed until data synchronization is completed. When you manually synchronize after you update configuration values, the relevant data tables are updated and system-level caches are reloaded. When Max bootstrap objects are created, updated, or deleted, you must run synchronization to update the related data models.
The following metadata changes require manual sync to take effect:
• removed
• added
• renamed
• field_datatype
• relationship_type
• field_indexed
• relationship_dynamic
• object_physicaldelete
• relationship_ordered
• datatypeoption_datatype
• fieldoption_datatypeoption
• primitivetype_databasetype
• field_default_value_added
• fieldoption_value
 |
If you create a new calculated field and then run synchronization, the field is created as a new column in the table in the database. However, no values are populated in the column. To populate the column with calculated field values, use the Recalculate Field Value option in Object Designer. For more information, see Recalculating Calculated and Rollup Fields.
|
For more information: