BYOD - sales order lines v2 entity doesn't export to DB

(0) Share

Report

Posted on by migi111

485

Hi,

I have a strange error. I have published several standard entities to Azure SQL DB and they are also populated with the export job, but for some reason sales order lines v2 entity fails. I tried to export to xml-file and that was successfully completed. Does anyone have ideas where to seek the solution?

Thanks,

Migi

I have the same question (0)

All responses (10)

Answers (1)

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Migi,

First of all, you should try to regenerate mapping (Data management - Data entities - Modify target mapping - Generate mapping), re-publish entity, re-add entity to the data project and try to export again.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

Like (0)

Report

Hi Migi,

Can you go to the execution history or staging details to find an error message?

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

Hi Sergei,

I did all the steps, but still the same problem. Error msg is a bit strange:

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

Hi, it just says it didn't run. There's no log....nothing else

Was this reply helpful? Yes No
Verified answer

Sergei Minozhenko 23,093 on at

Like (0)

Report

Hi Migi,

What PU version are you using? I have the same issue before and it was related to fields in the entity disabled by configuration keys. If you marked "Skip staging" (can be added to the "Selected entities" grid via personalization), could try to unmark it and run export again?

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,032 on at

Like (0)

Report

seems some issue with schema difference between D365FO and BYOD

compare them using D365FO, republish and try export again

Was this reply helpful? Yes No
Suggested answer

Fangyuan Hou on at

Like (0)

Report

Hi Migi,

Agreed with Rahul & Sergei, normally when the error happens like: "An Error occurred in add data flow component for Entity Store", most of the case is because some issue with schema difference between D365FO and BYOD.

Un-publish & publish the entity from BYOD. Create new data project and add the entity to be exported. Once the entity is added to the project, have a check the mapping, remove the disabled fields from the mapping, remove the virtual field and use computed field instead of virtual field.

You can also have a try disable "skip staging".

Was this reply helpful? Yes No
Suggested answer

Rahul Mohta 21,032 on at

Like (0)

Report

let us know if dropping and republishing worked?

Was this reply helpful? Yes No
migi111 485 on at

Like (0)

Report

Dropping and republishing didn't work. I have created a support ticked to Microsoft.

Was this reply helpful? Yes No
migi111 485 on at

Like (1)

Report

Excellent...Thanks Sergei! I did the skip staging trick and found out the reason was crappy data. Almost half of the sales order lines had errors in validation so I changed the filter to run only the latest lines and....now it works :)

Was this reply helpful? Yes No