For this scenario, wouldn't it be easier for the third party to use the RESTFUL D365 F&O APIs that already exist and allow CRUD? As long as the third party has authority to access the D365 APIs, they can pull any data they want using traditional OData methods.
Hey, to skip the need of an apply to each you can use the Select action. Set the Select value as your dataverse output Value (dynamic content), then press the text icon next to the mapping field, and put the dynamic content you want there. This will create an array of the single field for each item in your Dataverse output.
@@Scott-Gaines I actually posted that before finishing the video. You can make it even cleaner by using the first function that you use in the Parse action as the value for the Select action. Thanks for these videos! Lots of helpful things I've picked up from them.
Nice video Scott. A more efficient way is to use a select clause in the oData. This way you don't return all fields from the vendor record - e.g. $select-'merp_vendoraccountno,merpaddress'. Can have a huge impact on performance, as your not returning a bunch of data you don't need. Best. mark
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
What do you think about this method for creating an API that a third party external system could send a request to and get back D365FO information?
For this scenario, wouldn't it be easier for the third party to use the RESTFUL D365 F&O APIs that already exist and allow CRUD? As long as the third party has authority to access the D365 APIs, they can pull any data they want using traditional OData methods.
Hello Scott, can you please point me to a video, where you read an API and add data to any table from dynamics365 F&O?
Hey, to skip the need of an apply to each you can use the Select action. Set the Select value as your dataverse output Value (dynamic content), then press the text icon next to the mapping field, and put the dynamic content you want there. This will create an array of the single field for each item in your Dataverse output.
Great thank you I'll give that a try.
@@Scott-Gaines I actually posted that before finishing the video. You can make it even cleaner by using the first function that you use in the Parse action as the value for the Select action. Thanks for these videos! Lots of helpful things I've picked up from them.
Is that correct that this flow only applicable for cloud deployment of Dynamics 365, and for on-permises it would'nt work ?
Nice video Scott. A more efficient way is to use a select clause in the oData. This way you don't return all fields from the vendor record - e.g. $select-'merp_vendoraccountno,merpaddress'. Can have a huge impact on performance, as your not returning a bunch of data you don't need. Best. mark
Be aware that the endpoint is not secured. Make sure to not expose critical data.
Good point!
Is there a way to make it secure?