Ability to Publish / Unpublish Duplicate Detection Rules

[joshcampbell191]

Hello,

I was wondering if there would be any interest in having a pipeline task that would publish / unpublish duplicate detection rules.

As it stands, it's not currently possible to export duplicate detection rules using the configuration migration tool unless the rules are in an unpublished state.

Having this task would allow users to automatically unpublish them before running the "Extract CM Data" task.

We would be more than happy to submit a PR for this task as long as you're okay with it.

Regards, Joshua Campbell

[WaelHamze]

@joshcampbell191 do you use the CRM package for any custom steps?

How do you see this task working? accepting a list of rule names and status?

[joshcampbell191]

We're using the CRM package to move the data (duplicate detection rules and other lookup data) across environments.

Our current implementation publishes / unpublishes all duplicate detection rules (this could be the default behavior) however, I believe that some users may want a whitelist / blacklist functionality.

[WaelHamze]

@joshcampbell191 if you can submit a happy I would be happy to review and merge.

I think we would need to find a way to make this configurable. perhaps a json string which contains rules and what state you would like them to end up in.

I guess with the option to unpublish all before the import.

Ideally you want want a smart way to detect if there are changes in the rules and then skip the update to the rule all together to save time. Because I think if you publish it will take time to regenerate the hash codes.

What do you think?