Custom Entity Fields Missing on Export

(0) Share

Report

Posted on by zachary.robinson@gt...

To preface, I am a novice at best on this subject. I have created a clone entity of an inventory transaction entity within Visual Studio in our dev environment; promoted successfully to production, and I can see the entity listed in the Data Entities list of Data Management in production. I can see all of the fields listed in this custom Inventory Transaction entity when using an Odata.Feed within Power BI.

The issue I am having is the export to our Azure SQL DB (BYOD) does not show all/any of the relevant fields of this entity in the Map Entity(Source) to Target (top picture). Nor does it show the fields from SQL Server Management Studio for this DB (bottom picture).

I am not certain if this is a Visual Studio, D365 of Azure SQL DB issue, but have successfully exported a multitude of other entities, and this custom entity has been the only one that does not export all fields that exist in this entity. As mentioned previously, and not sure if this correlates at all, I can see all of the fields from an Odata.Feed from Power BI when connected to the entity in the production environment of D365FO, so know that there are more fields than what is showing in the mapping picture above within D365 export project.

Any ideas on this?

Thanks!

I have the same question (0)

All responses (8)

Answers (1)

Suggested answer

Ajit 8,755 on at

Like (1)

Report

So you are seeing only one column in entity mapping? Try to regenerate the mapping from data entities form.

Was this reply helpful? Yes No
zachary.robinson@gt... 99 on at

Like (0)

Report

Ajit, thank you for your response, but I am not quite sure what you mean by this. Can you explain in more detail how to regenerate the mapping?

Was this reply helpful? Yes No
Suggested answer

Ajit 8,755 on at

Like (1)

Report

Sure. Navigate to Data Management workspace - Data Entities - Filter the entity which I have mentioned in 'Target entity

' form and then click on 'Modify target mapping' mapping form will open and you will see a button called 'Generate mapping'

Was this reply helpful? Yes No
zachary.robinson@gt... 99 on at

Like (0)

Report
Thank you for that. When I do this, I am only seeing one item available in the Staging Field, which is the reference category.

However, the Target Field column lists out all of the fields that I have listed in my custom entity of Visual Studio, and seen in Power BI Odata.Feed.

For further background:

the custom entity I made is made up of 3 tables in Visual Studio: InventTransOrigin, InventTrans, and InventDim.

The Data Management Staging Table for this custom entity is InventTransStaging.

A search for this staging table in the Data Entities list of Data Management returns the entity 'Inventory transactions originator'.

when exporting this, Reference Category is the only field listed

Reference Category comes from the InventTransOrigin table in Visual Studio

The target fields of the generate mapping page of D365 reflect the fields I have listed in Visual Studio for these three tables in my custom entity.

For my own understanding, does Power BI Odata.Feed connect to the Target while BYOD export does Staging? Is there a way to export 'Target' since I can see the list of fields of my custom entity there?

Thank you again for your help on this!

Was this reply helpful? Yes No
Verified answer

Ajit 8,755 on at

Like (0)

Report

Yes that's right. you should have columns in your staging table for BYOD push. Please make sure staging table is updated and if not, right click on your entity and click on update staging table (in VS)

Was this reply helpful? Yes No
zachary.robinson@gt... 99 on at

Like (0)

Report

Thank you for that.

I have updated the staging table within VS for my entity successfully.

Do I need to build/rebuild my solution and sync to database within VS? Also, will this need to be promoted again from dev up to Production?

Was this reply helpful? Yes No
Suggested answer

Ajit 8,755 on at

Like (1)

Report

Yes, Build, Sync and make sure your staging table updated with all columns. And yes you need to deploy code again.

Was this reply helpful? Yes No
zachary.robinson@gt... 99 on at

Like (1)

Report

Ajit, thank you very much for your help on this. I have refreshed the entity listed within the dev D365, and the mapping looks how I expect it to:

i have called for a code promotion, and standing by to see how this works. But, from what I can see in the dev environment of D365, your expertise and efforts have helped resolve this issue.

Thanks again!

Was this reply helpful? Yes No