AX2012 new field on InventTable is breaking the Replication of data to POS

(1) Share

Report

Posted on by Sophs@4Sight

223

Good day I am not sure this is the correct place, but I have an AX 2012 R3 question as I still have clients using this.

I added an indicator (YesNo) field to InventTable.

I then also added the field to the form EcoResProductDetailsExtended. I added this field to the user layer as this is a short term solution. (Busy upgrading to D365 FnO)

I teted and everything was fine. However when we deployed this change to Production (Live), the replication to their POS broke and the InventTable (N-1040) was cleared out.

So this meant that no Products could be seen on any of the POS tills.

Is there a step that I missed because this table is one of the tables being replicated?

Is it possibly because I added the field on the user layer?

Please can anyone assist.

Categories:

Microsoft Dynamics AX

I have the same question (0)

All responses (5)

Answers (0)

Jonas "Jones" Melgaard 4,985 Most Valuable Professional on at

Like (2)

Report

Adding a field to InventTable should not break the distribution jobs.

When did the distribution jobs run, and can you see any errors in the batch history for them?

I'm also thinking.... How did you deploy this change to PROD.

Full-on model store deployment with full CIL generation?

Was this reply helpful? Yes No
André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

HI Sophs,

I do agree with Jonas that adding a field should not break an integration. Was this the only change or were multiple customizations deployed to production? Having this field in a non-production environment is not causing this error? Have you tested this before moving to production?

Was this reply helpful? Yes No
Sophs@4Sight 223 on at

Like (1)

Report

Thank you for your responses.

As this is a very temporary solution, I only made the change on the usr layer. And imported my project. Compiled and synchronised the table / form and restarted the AOS.

The changes deployed was only a EDT (extending YesNO) and InventTable with New field and EcoResProductDetailsExtended, with field added.

I did not test the impact on the POS distribution in the Test environment, as I was not aware that it would be impacted.

Do you think it could be because it was deployed on the USR layer.

The distribution ran after my deployment.

Also when we removed my changes and ran the distibution jobs again all the InventTable had the data again.

Kind regards

Was this reply helpful? Yes No
André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi Sophs,

The deployment process to directly add the field in a production environment is wrong. Best practice would be preparing a full compiled and CIL built solution and move the model store from a sandbox to the production environment. Then a synchronization of the database.

Anyway, adding the field, even in the USR layer would most likely not impact the POS distribution. As this might be something specific to your environment, probably you can reach out to the POS vendor or the partner that was helping with the integration.

Was this reply helpful? Yes No
Raj Borad 1,428 on at

Like (0)

Report

Hi,

I think the issue is likely due to missing metadata sync and schema updates. InventTable is part of the Retail CDX (Commerce Data Exchange).

Adding the field in the USR layer alone doesn’t propagate changes to channel DB schemas or sync metadata used by CDX jobs.

This can result in replication jobs failing or clearing out data, as the schema mismatch causes the job to treat data as invalid.

What you should have done:
Add the field at a proper layer (preferably CUS or ISV).

Database sync may help for such issues.

Thanks,

Raj D Borad

Was this reply helpful? Yes No