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
I was trying to import JSON files using the Dynamics 365: Data Importer Release task. My file name was starting with the prefix "ExtractedData". It was neither importing file nor giving an error message/warning. Below is the log of import task
When I tried to import the same file with ExtractedData prefix using CDS data migrater import xrm toolbox it worked. Later, I changed the filename prefix to "ExportedData" and it worked from "Dynamics 365: Data Importer Release task". We should handle this and give an appropriate error message/ warning like No file found something like that.
The text was updated successfully, but these errors were encountered:
Thanks for raising this @vishnushukla. I feel this issue is best placed in the engine itself rather than the ADO release task which is just an interface to it. I'll transfer the issue.
tdashworth
transferred this issue from Capgemini/azure-devops-extension-xrm-release
Jul 22, 2021
tdashworth
changed the title
Issue on Dynamics 365: Data Importer Release task
No warning/error if data file can't be found
Jul 22, 2021
@vishnushukla Can you provide a zip of the config files and data you were using? Please try to keep the same file structure and also provide a full log from ADO.
I have been looking at the code and it should have logged out a message if there was no file.
I was trying to import JSON files using the Dynamics 365: Data Importer Release task. My file name was starting with the prefix "ExtractedData". It was neither importing file nor giving an error message/warning. Below is the log of import task
When I tried to import the same file with ExtractedData prefix using CDS data migrater import xrm toolbox it worked. Later, I changed the filename prefix to "ExportedData" and it worked from "Dynamics 365: Data Importer Release task". We should handle this and give an appropriate error message/ warning like No file found something like that.
The text was updated successfully, but these errors were encountered: