Recurring-Integrations-Scheduler
Recurring-Integrations-Scheduler copied to clipboard
microsoft
Idea: Possibility to use DefinitionGroupName from Manifest.xml as dynamic data project name
Hello. It would be useful to have possibility dynamic data project name. or example using DefinitionGroupName from Manifest.xml. In my use case I define one job per environment, which scans for packages and import them in environment. All import projects are named quite same. So data project get's populated with lot's of entities and it's hard to distinguish between different updates in history. As workaround I am using Description from Manifest.xml. Which can only be seen from "Data management" workspace Job history panel grid adding new description field from UI.
So adding a checkbox "Use DefinitionGroupName from Manifest.xml "somewhere near this "Data Project name in Dynamics":
Forgot to add screenshot of manifest (2). But we could also use file name for creating new data project (1)
As currently in the UAT lots of JOB history jobs with same name (Field description added manually in D365 UI)
But your solution seems to work quite well. If you start creating data projects with "dynamic" names then at some point you will have a lot of them and you will be in need of some cleanup solution. I do not see a convincing benefit here. What am I missing?
Yes, I see your point. It does not mean that every time RIS does this work a new data project is created. If one is found with same name it should reused as now. And it looks more tidy when splitting large data migration project between different DM project. At least one per module would be nice This brings to another inconvenience - currently data project contents get's cluttered with lots of data entities. It's not even possible to tell what kind of issue we had on previous import iterations, as entity mapping are being overwritten by latest import. Old and I think abandoned AX4 AX2012 X++ data migration tool "MS Dynamics AX 2009, 2012 Data Migration to D365 For Finance and Operations" (implemented by MS) also worked this way split imports by separate dat migration job runs. https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/data-migration-tool But it is really useful tool which helped me on few different data migration projects from legacy Ax systems.
Cluttered data project project example:
Hello. C# / .NET is not my developing language, but I did some copy pasting to achieve this: When _settings.DataProject == "DefinitionGroupName" Then extract Manifest, and take DefinitionGroupName as dataProjectName.
Attaching this change here to your judgment ;-)