Read on Twitter
Okay people!
New release of #d365fointegrations is out. This release is all about the future.
If you didn't know, the OData and Custom Service will soon start giving 429 (ToManyRequests) when being overwhelmed. We now support this. Follow the thread to learn more! #msdyn365fo
New release of #d365fointegrations is out. This release is all about the future.
If you didn't know, the OData and Custom Service will soon start giving 429 (ToManyRequests) when being overwhelmed. We now support this. Follow the thread to learn more! #msdyn365fo
So you need to fetch a lot of data from the OData endpoint?
Not a problem!
Use #d365fointegrations and get on with your work!
Get-D365ODataEntityData supports TraverseNextLink, for more than 5000 records, while respecting 429, with the RetryTimeout option to exit if early. 1/2
Not a problem!
Use #d365fointegrations and get on with your work!
Get-D365ODataEntityData supports TraverseNextLink, for more than 5000 records, while respecting 429, with the RetryTimeout option to exit if early. 1/2
The next thing is the ThrottleSeed parameter, will pause/sleep between calls, to lower the requests against the OData endpoint. 2/2 #msdyn365fo
So you need to import a lot of data against the OData endpoint?
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Import-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you smile
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Import-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you smile
So you need to delete a lot of data using the OData endpoint?
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Remove-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you forget the pain of deleting data
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Remove-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you forget the pain of deleting data
So you need to update a lot of data using the OData endpoint?
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Update-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you wonder how things can be so easy
Want to use the batch mode?
Not a problem!
Use #d365fointegrations and get on with your work!
Update-D365ODataEntityBatchMode together with the ThrottleSeed parameter will make you wonder how things can be so easy
So you are working with D365FO and OData, wanting to make sure you don't have errors because of 429 pushback?
Not a problem!
Use #d365fointegrations and get on with your work!
The (Non-Batch) Get-, Import-, Remove- and Update- cmdlets respects 429 pushbacks and will wait 1/2
Not a problem!
Use #d365fointegrations and get on with your work!
The (Non-Batch) Get-, Import-, Remove- and Update- cmdlets respects 429 pushbacks and will wait 1/2
for the next retry based on the value received in the header of the response. It will keep trying, respecting new pushbacks. RetryTimeout offers you the option to fail the request if it takes to long. Keeps your code nice and clean. 2/2 #msdyn365fo
Did you know that #MsDyn365FO / #MsDyn365SCM & #MsDyn365HR share the same OData architecture? This means that #d365fointegrations is the single tool you need to work with all mentioned platforms. #OneStopShop
