DMF/DIXF - Update target table by using a strongly reduced mapping does not work

(0) Share

Report

Posted on by RIF

I’m trying to set up a permanent interface for item import into AX using DMF/DIXF.

We have two different scenarios : The first case is a new item coming from an external PLM-software. This one will be imported via DIXF using 100% staging-to-target-mapping. The product staging table gets filled by the PLM-data and an AX-item template first. Works good.

Second scenario is the „Update-case“ afterwards. The same item comes from the PLM-system once again, with just a couple of updated fields. No AX-item template is used, so the staging table is almost empty except the mandatory /updated fields. Copying this to target by using the same definition group leads to overridden empty target fields, whereever the staging is empty and the target not.

Now I’ve tried to resolve this problem by using another definition group with another target entity where a strongly reduced target mapping to the product is behind. Just a couple of fields are mapped from staging to target and, lets say, the generator for product language text translation is active.

But this won’t work as expected, I always get error messages like this :

«A record in ecoResStorageDimensionGroup could not be created. The record already exists.«

«A record in ecoResTrackingDimensionGroup could not be created. The record already exists.«

The parameters for insert() / validateWrite execution logic in DMF are turned off, but this makes no difference.

I do not know why the DMF target job is trying to create these tables with empty values because the item is already available in AX and there is no target mapping for ecoRes*DimensionGroup tables or generators active.

I’m using Dynamics AX 2012 R2.

Thanks in advance,

Best regards,

Frank

*This post is locked for comments

All responses (3)

Answers (1)

RIF 60 on at

Like (0)

Report

RE: DMF/DIXF - Update target table by using a strongly reduced mapping does not work

Thank you very much, finally the following minimal configuration worked for me to update the items in AX:

- I kept the Generators for data area ids

- The item id is always available in the source file, so it could be used as DisplayProductNumber and for mapping purpose to the other related datasources

- The mapping to the item translation is just to test if the update works

- The only one thing I have to do is updating the fields EcoResStorageDimensionGroup_Name, EcoResTrackingDimensionGroup_Name, GroupId (for InventFiscalLIFOGroup) in the staging table after import by using the values from the original AX item to avoid that anything will be overridden with empty values.

Based on this, I have only to add the fields which need to be updated or self-created generator logic.

Thanks once again,

Best regards,

Frank
Suggested answer

Community Member Microsoft Employee on at

Like (0)

Report

RE: DMF/DIXF - Update target table by using a strongly reduced mapping does not work

For this issue you need to create separate entity as this entity which you are using is having related tables as target query, hence it is trying to create data in other table.

Please verify and update us with your finding and let me know if you need any support creating new taget entity
Verified answer

gfadden400 on at

Like (0)

Report

RE: DMF/DIXF - Update target table by using a strongly reduced mapping does not work

Frank -- We had a similar requirement in our organization, to have a separate "update" job on items. You're definitely correct in creating a new target entity that is strongly reduced...this is exactly what we did as well. However, you'll want to maintain all the functions on the stock item entity for it to play nice. We ran into similar errors, and just ended up recreating a new target entity but keeping all stock functions in the entity...that did the trick.