You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Schema validation is failing while exporting data from the environment
Missing entity got removed, but schema validation is still failing
Hey, I'm facing the problem in my pipeline while exporting data from my environment. The error occurs in the following pipeline task: PowerPlatformExportData@2 (error message is in the screenshot below).
The export schema includes the required entities with it fields and got multiple times validated. Though, the following error occurs again and again.
Although the export succeeded by using the manual workaround of pac tool cmt (Configuration Migration Tool).
Therefore, we decided to remove the problem causing entity from the export schema in order to let the pipeline run again if the error still occurs. But the error is still appearing in the pipeline, which makes no sense.
Screenshots
Thank you for your help
The text was updated successfully, but these errors were encountered:
JulianRn
changed the title
ExportingDataTask from Dynamics365 environment
ExportDataTask reports failed schema validation because of missing fields although they are included
Nov 13, 2024
Describe the bug
TL;DR
Hey, I'm facing the problem in my pipeline while exporting data from my environment. The error occurs in the following pipeline task: PowerPlatformExportData@2 (error message is in the screenshot below).
The export schema includes the required entities with it fields and got multiple times validated. Though, the following error occurs again and again.
Although the export succeeded by using the manual workaround of pac tool cmt (Configuration Migration Tool).
Therefore, we decided to remove the problem causing entity from the export schema in order to let the pipeline run again if the error still occurs. But the error is still appearing in the pipeline, which makes no sense.
Screenshots
Thank you for your help
The text was updated successfully, but these errors were encountered: