Share
Report
20Hey Dynamos:
I'm trying to better understand reference data in Dynamics system settings, transferring that between environments, and why certain processes involving reference data require manual tweaks when importing.
So, "reference data," in my case, are a list of QUEUES and SUBJECTS that have been created in my sandbox dev environment through System Settings > Service Management.
I'm aware that tools exist, such as XRMToolKit and the MSFT Data Migration SDK tool, to export and import data such as this. XRMToolKit is too complex for me right now, and the MSFT SDK doesn't always get the job done. Someone who I work with has exported the metadata for Queues and Subjects from dev, into a CSV, which then gets imported into the UAT / Prod environment.
Ok, so that data has been imported. Here are some queues, imported through CSV.
Then I go to import my managed solution. Import with no issue.
I have Route Rules (which can be added into the solution layer directly) that call upon and use Queues (which were imported manually). The Routing Rule itself imports, but I have to enter each rule item and *reassign* the Queue to it.
For example:
Here's a Routing Rule, complete, in my dev sandbox:
- Routing Rule imported through solution
- Queues imported through CSV
And when import completes I've got:
Then I need to enter each Rule Item, reassign the queue, save, rinse wash repeat.
If the reference data is exported from dev sandbox specifically to maintain GUID and other stuff across environments, then why does the workflow continue to need to have items re-asigned?
Can anyone help me make sense of how this process should work?
All responses (
Answers (
