Microsoft Dynamics AX (Archived)

why recId is mandatory in Excel Add-in for some tables?

(0) Share

Report

Posted on by Lakshmi Karambakkam

1,307

Hi,

We recently upgraded to AX 2012 R3 CU11 update. this problem was not there with our AX 2012 R3 previous CU.

We have planned to use excel add-in for importing Item allocation keys (so we have to use two tables) ForecastItemAllocation and ForecastItemAllocationLine and I found recId as one of the mandatory fields to be imported.

RecId is a system generated AX field and will not be imported from the legacy system. Then how come RecId is given as a mandatory field ?

Also without filling RecId column, the add-in functionality is not importing data into AX fields, tables.

Why RecId is added as a mandatory field?

Thanks,

Lakshmi

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Mea_ 60,286 on at

Like (0)

Report
Copy link

Link copied!

Hi Lakshmi Karambakkam ,

You can enter any random int value in RecId field and AX will generate proper RecId fro you.

Please remember that direct import to AX tables is possible only for System admin user, so AX assumes that you know what you are doing. Usually you should use AIF services or document queries exposed through excel because they have business logic and validation behind and also they have "user friendly" structure and do not expose system fields like RecId.

Was this reply helpful? Yes No
Lakshmi Karambakkam 1,307 on at

Like (0)

Report
Copy link

Link copied!

Hi Ievgen,

I tried using random value for recid and it has now thrown a different error.

But all the fields have valid data. So I am not sure what this error meant?

I looked into ForecastItemAllocationLine table\Index. the unique index has recid as a field.

This looks so inappropriate. If recid is added, any index will be unique. But added it to a setup table, I see no particular reason . I think this is the reason that Recid has come as a mandatory field in Excel add in.

As I said, we recently had CU11 update. In CustVendExternalItem table properties, recId is set as Prrimary Index. So I had the same problem. So I changed the Primary index to another index and now Recid is not a mandatory field in Excel add-in.

Please correct me if my understanding is not correct.

Is this a glitch in CU11 update. Is there any fix for these type of tables or any alternate way of avoiding this RecId field ?

Thanks,

Lakshmi

Was this reply helpful? Yes No
Mea_ 60,286 on at

Like (0)

Report
Copy link

Link copied!

I mean random recid for each row. Did you try to do it on 1 row ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hello,

You can change the PrimaryIndex, this way the recid will not be a key anymore. If you don't want to change the table, then, add a new table and insert in the new table, create a job to insert the data from the new table to the ForecastItemAllocationLine.

Or create your own Importation tool framework, I can help you with that.

Was this reply helpful? Yes No