118
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
Category: Data Management
STATUS DETAILS
Needs Votes
Ideas Administrator

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!

Comments

F

We have created a Visual Studio package solution that does this very thing.

And it has been tested and used on Dev/Test environments.

So, it is possible.

Category: Data Management

F

Sorry but the statement from "Administrator" is not covering this topic here and I cannot understand why 88 votes are made obsolete.


1 - creating a link between D365FO and Dataverse environments with option to specify companies

  • To be automated, just give us API params to define source and target and it could be worked in easily in our pipelines.

2 - unlinking environment

  • To be automated

3 - clear dual write tables in D365FO and Dataverse

  • Already happening on linking currently but the notification after linking could be improved (when the progress at all is working)

4 - running mappings including the options to specify the intial sync

  • To be automated, at least the version without the initial sync (regular activity for each migration when GOLD-->MIG copies are ongoing)

5 - applying a solution

  • To be automated, just prepare API params to define versions

6 - stopping mappings

  • To be automated (same as button functionality)

7 - pausing mappings

  • To be automated (same as button functionality)

8 - changing the version of a mapping

  • I agree here, this must be tested upfront in lower envs. No automation needed from my point of view.

9 - updating the current version of a mapping after a new version of a solution has been applied

  • I agree here, this must be tested upfront in lower envs. No automation needed from my point of view.


So from 9 recommendations, 7 are totally valid. Can we please reopen this item or do we now have to maintain the next Ideas like https://experience.dynamics.com/ideas/idea/?ideaid=2f777091-6dba-ec11-bea1-0003ff45dadf


Category: Data Management

F

This needs to be a base feature in order to any type of CI/CD automation. Requiring someone to do steps manually defeats the purpose of being able to automate deployments.

Category: Data Management

F

This would be a dream come true.

Category: Data Management