Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
Greetings. I am attempting to perform a data upgrade from an AX 4.0 environment to an AX 2012 environment. I have completed the upgrade preprocessing checklist in 4.0, and am running through the data upgrade checklist in 2012, but am having an issue with the "Generate table mappings" step. A large number of tables are reporting an error "No mapping" for the field CREATEDDATE. I see that CREATEDTIME is successfully mapped to DEL_CREATEDTIME, but no similar such field has been created for the date. I could go ahead and delete all the CREATEDDATE fields in my 4.0 system, but that seems like a silly way to resolve this issue. Has anyone else encountered this? Is there any recommendation for resolution?
Check the setting of CreatedDateTime property for the table in AX 2012
Are all of these tables custom tables or ones that you had modified to add the option to track Created Date and Created Time within AX 4.0? If so, the code upgrade process of importing the AOD file where you made these changes and then using the Code Upgrade Project are what automatically create those DEL_CREATEDDATE fields (same is true for DEL_MODIFIEDDATE).
If you can't go back to the point where you are able to use the code upgrade project approach, you will need to write a pre-synchronize script within Dynamics AX 2012 that will list each of those fields and the option to not bulk copy each field. Look at the updateMappingCompanyInfo method of teh ReleaseUpdateDB60_Administration class for an example that is similar.
Thank you for your response!
While there are some custom tables (in which case I am not surprised to have mapping issues) the ones I was most keenly interested in are those which are purely native 4.0 tables with no customizations, and still are not properly mapped. I'll have to look at pre-synchronize scripts, and will post results.
I was wondering if you ever found the cause and/or sollution for this one. I'm encountering exactly the same issue on 185 tables. In my case modifiedDate and CreatedDate. All these tables are native AX 4.0.....
If you have more info I would appreciate it.
Gerard - if the fields that are not mapped are the ModifiedDate and CreatedDate, one possible scenario we have seen that causes this is if you had a some sort of issue with the transfer of your SQLDictionary table into the DEL_SQLDictionary table during the Connect to Source Database step of the 2012 checklist. You could try doing the following SQL statement to see if your data fits this pattern,
select * from DEL_SQLDictionary where FieldType = 3 and Flags = 0 and Name in ('MODIFIEDDATE','CREATEDDATE')
If you see the same tables listed here that show up on your mapping errors list, you can do the following update statement and try mapping it again - long term you should investigate why your DEL_SQLDictionary table might have had issues (wasn't synched on 4.0 for example).
update DEL_SQLDictionary set FieldType = 6 where FieldType = 3 and Flags = 0 and Name in ('MODIFIEDDATE','CREATEDDATE')
Ordinarily this transformation happens as part of the updateTimeZoneTablesToBeUpgraded method of the RelaseUpdateDB41_Basic class that runs during the Pre-Sycnhronize scripts.
Then you can try and regenerate the mappings to see if it removes those errors. However, this is a temporary workaround, not a long term solution - so if this happens on your next upgrade iteration, you should open a support case for further investigation.
Thanks for your reply and I think you're right:
At first I had an issue with two customized fields. After solving those (exclude from bulkcopy in upgrade script) I got the 185 modified/created date errors.
I started a completly new migration which finished this morning and the errors are gone. I had one error left with a customized table, but was able to fix that. No errors anymore,
I think I made a mistake in the first run after solving the first errors with the two customized fields. Althiough I'm not sure what I did wrong. Advice when you encounter an error like this: Restart you're whole process from AX4 (in my case),
I've kept the previous databases. If I have some time left I'm going to restore them and try your SQL scripts. I will post the results here.
Regarding the upgrade platform: Now it's finished it looks like 99% of all data has been migrated correctly. But it took me a lot of time to get how it works. Mainly on the cutomized parts. Pro platform: When it works it works very good. Con platform: It will take time and effort to understand it and get it to work correctly.
Thanks and cheers,
can anyone tell me how to write scripts for customized tables and fields.
The best sources of information are found at How to Write Data Upgrade Scripts for Microsoft Dynamics AX 2012 and http://blogs.msdn.com/b/axsupport/archive/2012/02/09/writing-data-upgrade-scripts-part-1-understanding-the-components-of-the-process.aspx
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13