123
The current options to automate the application lifecylce management for Dual Write integrations are very limited.
Please add options to automate all ALM steps.
Currently, the export and import of a solution that has custom Dual Write mappings can be automated.
The following can not be automated:
- creating a link between D365FO and Dataverse environments with option to specify companies
- unlinking environment
- clear dual write tables in D365FO and Dataverse
- running mappings including the options to specify the intial sync
- applying a solution
- stopping mappings
- pausing mappings
- changing the version of a mapping
- updating the current version of a mapping after a new version of a solution has been applied
Please add options to automate all ALM steps.
Currently, the export and import of a solution that has custom Dual Write mappings can be automated.
The following can not be automated:
- creating a link between D365FO and Dataverse environments with option to specify companies
- unlinking environment
- clear dual write tables in D365FO and Dataverse
- running mappings including the options to specify the intial sync
- applying a solution
- stopping mappings
- pausing mappings
- changing the version of a mapping
- updating the current version of a mapping after a new version of a solution has been applied
STATUS DETAILS
Needs Votes
Administrator on 11/16/2021 8:13:13 PM
Manual uptake on new versions of the mapping is a mandate as each map version potentially brings new features or enhancements. The customers must test these maps in their dev box before promoting to production. So there is not much we can do here!