One of my client is having an issue about choosing best way to load Setup tables, Parameter tables, Workers, Employers, Assigning users and etc during go live. We have lot of data for these to be loaded. We are unable to use DIXF for loading Employers, users , assigning workers etc because DIXF doesnt support inheritance tables(Ex: DirParty, DirPerson etc...). The only option we have left is by manually entering, but it might take few days which is not a considerable option for go live. Can some one please suggest what would be the best approaches for loading these above mentioned data. etc.
We are using Dynamics AX 2012 R2.
Thanks in advance.
you can use excel add in if you are finding problem with DIXF
here is one of the many links which will guid you for excel add ins. hope it will help you
Your information about DIXF isn't correct. For example, the Employee entity is included in AX out of the box. There are also many other entities based on DirPartyTable, such as Customer.
I think you mean that the wizard for custom entities has some limitations, but it doesn't mean that such entities can't be created nor that the framework can't use them.
Some teams prefer preparing the data in a separate database and then copying the whole database as the starting state of the production environment.
You must somewhere have a database where you're preparing and testing the data, mustn't you?
Your remark suggests that you also need to export some data from another system, which wasn't included in your original question. (I wouldn't even consider updating a database which already contains transactions.)
If it's the case, I would start with an empty database, use DIXF to export and import the data from your other live system and manually set up things that are specific to the given instance. I would also periodically copy the DB to a test system, where the correctness would be verified. When ready, I would put the DB to the new production system.
Aha, your original question gave me a completely different impression - I would think you already have things like workers if you're using the system for a year and the title even say "at Go live Date". All right, we're not talking about preparing a system for going live, it's about importing data to an already life system. DIXF is still the best tool you have for data imports, and what you're describing doesn't sound like large tables, so you should have no problems importing it to production in a two days. Anyway, you can test it many times before to see if performance is all right.