Changed displayed value of trigger state in case it is Blocked. Now it says Executing. "Blocked" was misunderstood by users.
Implementation of error keys file for failed or partially failed imports.
Cleanup of validation procedure. Removed some dubious checks.
Corrects interval in export job
Ignores bad requests of GetExecutionStatusSummary request which sometimes returns Bad request. In such cases job will just retry request.
Updated Quartz.Net to 3.0.6
Updated Polly to 6.0.1
Updated ADAL to 3.19.8
Retarget whole solution to .Net framework 4.6.1
In some scenarios it happens that the Exceptions are not logged because of the fact that the Exception message is empty.
This changeset will enable exception logging for the import jobs even when the exception message is null or empty string.
In some scenarios it happens that the Exceptions are not logged because of the fact that the Exception message is empty.
This changeset will enable exception logging for the import jobs even when the exception message is null or empty string.
This change makes an extra option available to be able to configure the relative path to the OData actions of ImportFromPackage (Import jobs) and ExportToPackage (Export jobs) actions through the user interface. The configuration is made available through the "Options" button which is available for import/export jobs.
Please note that Upload/Download jobs are not in the scope of this change and remain unchange from configuration point of view.
We do not need to send the `x-ms-version` header, as the SAS token
already contains the necessary version information for the Blob storage
endpoint. This fix will make DevBoxes work with Azure Storage Emulator.
Based on the request of https://github.com/TomekMelissa the feature to initialize the relative path to the ImportFromPackage is removed to make the merge of this fork easier to the Microsoft-master
To increase the traceability of the files getting uploaded to D365FO, the Manifest.xml file is getting updated with the original file name before uploading the data package. Offcourse this change is also using the original file name in the data package for the data file itself. This happens right before the upload of the data package which is getting prepared based onthe template file name.
This change will use the configuration from the RecurringIntegrationsScheduler.Common.dll.config to get the ImportFromPackage relative path from the configuration file, if defined. If the value is not defined in the dll configuration file, it will use the original value.
This feature helps you implementing a custom version of ImportFromPackage.
Tomek Melissa
rubenis
Caleb Blanchard
MZade
Andreas Nielsen