We got the below error while trying to set a lookup field because of the incorrect syntax. or The incorrect syntax / formula – It should be either logicalcollectionname(GUID) Or logicalcollectionname/GUID https://nishantrana.me/2022/06/20/fixed-resource-not-found-for-the-segment-in-power-automate/ After setting it correctly, the flow ran successfully. Hope it helps..
Continue Reading Nishant Rana’s Article on their blog
Fixed – URL was not parsed due to an ODataUnrecognizedPathException or Bad Request – Error in query syntax (Power Automate)
We got the below error while trying to set a lookup field because of the incorrect syntax. or The incorrect syntax / formula – It should be either logicalcollectionname(GUID) Or logicalcollectionname/GUID https://nishantrana.me/2022/06/20/fixed-resource-not-found-for-the-segment-in-power-automate/ After setting it correctly, the flow ran successfully. Hope it helps..
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)
Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate
