The migratory pattern of a database row in AX |
One of the more monotonous steps, should you be migrating data across multiple companies, is creating the data definition groups and adding the same entities to the group, but presumably with different parameters to import into the Staging table. Example below where we use a stored procedure with a parameter to separate data across legal entities:
With a DSN datasource calling a stored procedure, passing in a company data area identifier |
There exists another option, however. Why not get someone clever to write some X++ to just duplicate the whole definition group to another, empty group:
Highlighted is our source group with the parameter that we are replacing |
In the example above, the Asset table entity had a DSN datasource query as the following:
EXEC HIEAssetTable 'HAL'
Updated in the destination to:
EXEC HIEAssetTable 'ZZZ'
Finally, when copying DMF configuration data across AOS instances, we could also try to use the DMF framework itself to export then import the DMF data into a different installation?! The concept makes my head hurt so I asked a colleague to set it up and it works. Use at your own risk:
Configure a DMF group, to set up your DMF data how you like it (AX 2012 R3 CU8 example). |
No hay comentarios:
Publicar un comentario