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
for testing purposes I am trying to import multiple BOM versions against a single BOM. (1 item -> 1 BOM -> Multiple BOM versions)
The file I am importing contains just 2 rows of data against 1 BOM
and ITEM and the rows have different To & From dates and Active
To my mind that should be what is required to represent an obsolete BOM version and a current BOM Version.
However, when I do "Get Staging Data" it fails with a Primary key violation "Cannot insert duplicate key in to object dbo.DMFBOMVERSIONENTITY"
The primary key on DMFBOMVERSIONENTITY is:
ALTER TABLE [dbo].[DMFBOMVERSIONENTITY] ADD CONSTRAINT [I_100994ITEMIDX] PRIMARY KEY CLUSTERED ( [ITEMID] ASC, [BOM_BOMID] ASC, [EXECUTIONID] ASC, [DEFINITIONGROUP] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]GO
I have no idea what EXECUTIONID or DEFINITIONGROUP are, and for my purposes it doesn't make sense that ITEMID or BOM_BOMID should be different.
Ignore EXECUTIONID and DEFINITONGROUP, they are used by the data migration framework to manage data migrations. Include FROMDATE and TODATE in your index to make it unique(...er). If that does not solve your problem, take a look at the find method of table BOMVersion to find out what makes a record in this table unique.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13