web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

Trouble translating an export to BYOD, to an export to Datalake for ProjectStaging

(0) ShareShare
ReportReport
Posted on by 158

We're switching from BYOD to Datalake.  Most everything has been exported fine, except one: 

ProjectStaging - which here you can say has 'sortingid1', 'sortingid2', 'sortingid3'
FO-Data-Management-ProjectStaging.JPG

In exporting to BYOD, I see it here

FO-_2D00_-Projects-Datalake-Export.png

And OK:

Staging Table: ProjectStaging = Entity: Projects. 

Seemingly 'entity' is the name I want, to translate over to the Datalake Export screen. 

Go over to Export to Datalake, there are several Entities named 'Project'. I assume ProjectEntity is probably the one I'd want



I do see, in our storage account, a definition for ProjectEntity in Entities/ProfessionalServices/ProjectManagementAndAccounting

But that definition is missing SortingColumn1, SortingColumn2, etc. 


I am doing this by feel - which has worked mostly, but not on this one. I'm not clear if I'm grabbing the wrong entity, or if the entity is correct, but is (somehow) exporting with some of the definition missing / what to troubleshoot. 

I have the same question (0)
  • bbb0777 Profile Picture
    158 on at
    RE: Trouble translating an export to BYOD, to an export to Datalake for ProjectStaging

    I did just notice.

    One folder down

    Entities/ProfessionalServices/ProjectManagementAndAccounting/resolved

    There's a second projectentity.cdm.json file

    And this one has additional lines that do mention SortingID1, etc.



    Though idk what this means - 


  • Suggested answer
    Mohit Rampal Profile Picture
    12,565 Moderator on at
    RE: Trouble translating an export to BYOD, to an export to Datalake for ProjectStaging

    Hi, ProjectEntity is the correct data entity and  SortingColumn1, SortingColumn2 are Virtual fields in Data entity. When we select Data entity from 'Choose using entities' all underlaying tables are exposed. But since this fields are not mapped fields with DataSource table, I think that's why its not exposed.

  • bbb0777 Profile Picture
    158 on at
    RE: Trouble translating an export to BYOD, to an export to Datalake for ProjectStaging

    Mohit Rampal

    Thanks!  The SortingColumn1 & SortingColumn2 did successfully export to ProjectStaging in our BYOD

    Not so sure then, how can we recreate ProjectStaging (with those virtual fields) in the Datalake Export?

  • Mohit Rampal Profile Picture
    12,565 Moderator on at
    RE: Trouble translating an export to BYOD, to an export to Datalake for ProjectStaging

    Since data entity itself is used in BYOD so virtual fields will be exported. For Azure Data Lake, you can create table fields and add logic before insert to populate those fields. Also have to run script to populate data for existing records. I couldn't find any way that MS recommends to handle virtual and computed fields in azure Data Lake.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 667 Most Valuable Professional

#2
CU05031448-0 Profile Picture

CU05031448-0 584

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 554 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans