[W1][Table][5330][CRM Connection Setup] Add Event to Skip ResetSalesOrderMappingConfiguration

[az-ha]

Why do you need this change?

When enabling CRM Connection Setup, all table mappings, field mappings, and job queue entries are reset to their default values.

With every major Business Central update, we are required to redeploy the CRM solution to upgrade it to the latest version. This process forces us to:

1. Disable the CRM Connection
2. Redeploy the solution
3. Enable the CRM Connection again

Re-enabling the connection always resets all customer-specific mappings and job queue settings. This frequently causes sync issues such as duplicate records and overwritten data.

To mitigate this risk, we need a way to skip the automatic reset of the CRM configuration during re-enablement.

The main ResetConfiguration function in the CRM Setup Defaults codeunit already contains an event

However, the Sales Order mapping is reset in a separate location, directly in the OnValidate trigger of the "Is Enabled" field. This reset cannot be bypassed, which makes it impossible to fully prevent the configuration reset even when handling the main reset through an event.

Describe the request

We need to be able to skip the line CRMSetupDefaults.ResetSalesOrderMappingConfiguration(Rec)

A new event with an IsHandled above this line would be enough. Alternatively, an event could be added inside the ResetSalesOrderMappingConfiguration function in the Codeunit "CRM Setup Defaults":

Internal work item: [AB#616640](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/616640)

[AleksandricMarko]

Hi @az-ha,

Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Performance Considerations: Expected execution frequency and potential impact assessment.

• Data Sensitivity Review: Confirmation that no sensitive data is exposed through this event, or rationale if sensitive data access is necessary. Please confirm whether the CRM Connection Setup record passed to the event contains any sensitive configuration data.

• Multi-Extension Interaction: Please describe potential risks if multiple extensions subscribe to this event and how conflicts would be mitigated. For example, what happens if multiple extensions each want to handle the reset differently?

Please update the issue with the missing details. We'll automatically re-analyze once updated.

[az-ha]

Hi @AleksandricMarko

Thanks for the quick reply.

• Performance considerations: The event would only execute when the CRM Connection Setup is enabled or re-enabled. The performance impact should be exactly the same as in the ResetConfiguration function in the CRM Setup Defaults codeunit, which already contains an event with the same behaviour. Performance impact is negligable.
• Data Sensitivity Review: The same as in the ResetConfiguration Event. No sensitive data is exposed.
• Multi-Extension Interaction: It would have the same behaviour as the ResetConfiguration Event, as we only need the parameters CRM Connection Setup and IsHandled. Other extensions should be aware of the IsHandled design pattern.