Finance | Project Operations, Human Resources, ...

Reference field between tables in different companies showing blank alternate key

(0) Share

Report

Posted on by Sarah Ryan

257

I have a custom table that has the 'Save data per company' property set to 'Yes', and a standard table that has this value set to 'No'. I have added a reference field on the standard table using the recId field of my custom table. I created a RefRecId EDT with the reference table set to my custom table. My custom table also has an alternate key based on the natural key. This has automatically added the natural key to the 'AutoIdentification' field group as well.

When I look at the data in the standard table in the SQL database, I can see that the RefRecId reference field I added has been populated with RecId's from my custom table. So far so good.

When I look at the standard form where I have added my reference field/group, I am expecting to see the alternate key value populated. All I see is a blank value! The strange thing is, is that when I select the value, close the form and open it, I can see the alternate key value has saved, but there is nothing different when I look back at the SQL table.

The only different thing I can see here is that the data was imported using the data management framework and in a slightly older version of D365 FinOps. I recently upgraded to version 10.0.13 with platform update 37.

Has anyone else seen this issue before? If so, how did you manage to overcome it?

Thanks in advance.

Sarah

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Sarah,

If the standard table is global and your table is company specific, what exact data needs to be presented here? Are you taking care of setting the context correctly for the current legal entity? Your scenario might cause performance issues when deleting a record from the standard table. If there is a delete action, the delete process will loop through all legal entities.

You can probably better create a global table and add an own field for the legal entity. It would solve potiential performance issues and it might be easier to set the filter on the correct legal entity.

Was this reply helpful? Yes No
Sarah Ryan 257 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre`

The reference field is only available in the context of the 'AU' country region.

To provide some context around this scenario, my reference field is on the 'PayrollEarningCode' table. It points to a table containing data that is specific to Australian entities only.

The odd part about this is that when I reselect the value that is already saved in the standard table, I can then see it without any issues. I cannot see anything different in the SQL database. Also, I checked that the reference recId on the standard table actually matches a record in my custom table.

Was this reply helpful? Yes No
Sarah Ryan 257 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre`

On further investigation it seems that something may have gone wrong when I processed my latest upgrade. I imported the data again via the data management framework and its fine! In saying that I still cannot see what is missing in the backend that would cause this.

Was this reply helpful? Yes No