Share
ReportOur client is running D365 on-prem.
We have exports of several data entities to a BYOD (an Azure SQL DB), set up as daily batch jobs.
This was working in PU36. After we’ve upgraded to PU39, the exports are failing.
For each entity there are two errors in the execution log, both on the Target stage:
- Package Execution Failed for Entity Store
- BYOD export failed on final attempt. Could not generate export file for entity 'xxx' for job 'YYY’
Steps that I’ve done to try and solve:
- Refreshed entity list
- Republished entities, edited change tracking and republished.
None of these worked.
We’ve even created a new byod, published some entities and exported. The errors still remain.
What is puzzling is that the staging tables are created in the byod upon publishing (so the connection is valid). Checking the tables in the byod, there are some tables with data and some that doesn't have data in, however on D365 in data management the job shows as failed for each entity.
Has anybody had similar issues with exporting to a BYOD after an upgrade, or on PU39 specifically?
All responses (
Answers (
8,755
