Missing SortId fields in ProjTable exported on Azure Synapse link

(1) Share

Report

Posted on by Balasubramanian R

Hi,

On D365FO, does anyone face a situation on missing SortId fields on the ProjTable exported to Azure Synapse link? We have data in those fields that are required for reporting. Any help is appreciated.

Thanks,

All responses (2)

Answers (0)

t4m7 61 on at

Like (0)

Report

Missing SortId fields in ProjTable exported on Azure Synapse link

Hi - I can also confirm that while i can see the 3 sortingid fields in the projtable in F&O, i do not see them in our OneLake.

I do think there is something odd about those fields.

1. If I look at projtable in the sysTableBrowser, all 3 have the same title "sortingid" even though the underlying field is sortingid_1

2. Some time ago, we were unable to update those fields via the F&O connector...but we are able to update them using the Dataverse connector and virtual entity.

I'm not a dev, so sometimes we have to do workarounds, so we are pulling that info via dataverse when we need it, but if you have a dev on your team, i suspect there is something funny about how those fields are defined in the first place...maybe they can check it out.
ShahzaibAhmed52 117 on at

Like (0)

Report

Missing SortId fields in ProjTable exported on Azure Synapse link

If Azure Synapse Link is configured to exclude certain fields, you may need to review the export schema to ensure the required field is mapped correctly. It's possible that customizations or filters were set up to limit fields for export, excluding those fields