Rajeev Pentyala – Dynamics 365 Blog:
In this article, I am going to discuss about transaction aware batch processing in ExecuteMultipleRequest using ExecuteTransactionRequest.
Is ‘ExecuteMultipleRequest’ not a transaction aware?
- By design, ‘ExecuteMultipleRequest’ is non-transactional.
- Which means ‘Request’ objects added to ‘ExecuteMultipleRequest’ are independent of each other and if any exception occurred in any of the ‘Request’ will not roll back previously committed ‘Requests’.
- However you have an option to stop the batch (i.e., By setting ContinueOnError = false), if any exception occurs.
- Important to note is that, this behavior is not a transaction aware and ‘Requests’ executed prior to the error, will still be committed.
How can we achieve ‘Transaction’ in Batch execution?
- Using ExecuteTransactionRequest, we can achieve ‘Transaction’ (i.e., Commit and Rollback) in Batch execution
- ExecuteTransactionRequest will execute the all the ‘Requests’ in a single transaction.
- If any exception occurred in any of the ‘Request’ execution, will roll back all the previously…
View Original Post
Hope this helps…
After knowing the wide advantages of reporting with the help of Data export service, I would like to share some tips and valuable resources for the same.
This Data export service in D365 by MVP Scott Durow is the first step to jump start your learning, people preferred to view instead video can better go through this Data export service blog content from MVP Nishant Rana.
Edit: 20 April, 2018: Suprizing what was Azure Key vault? Azure Key Vault helps safeguard cryptographic keys and secrets used by cloud applications and services.
Followed the steps mentioned, however I still used to receive error Unable to connect to the Destination mentioned in the Keyvault URL while configuring the data export service taken from the Secret Identifier in Azure obtained after running the Powershell script with all the details filled in.
I followed the fix provided in this Unable to connect with KeyVaultURL, but it didn’t help in my case.
Point to note for creation of this feature:
1.Don’t forget to create the login & username for the new Azure SQL Database, this is needed for the secret vault to communicate with the destination organization to load data.
2. After copying the Database connection string as mentioned, don’t forget to change the Username & Password in this string with details you had created in above step and don’t try with D365 login permissions.
Then I was able to validate the Keyvault URL successfully. Currently my Azure subscription is in South India, but still this data export feature works successfully.
Hope this helps someone trying to configure the Data export feature of Dynamics 365.