Fix GUID format mismatch in SYNC HELPER - Cloud Flows #10785
+203
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SYNC HELPER - Cloud Flows fails when processing flow IDs from Power Automate API because they lack hyphens (
1a13663fde2d4a0fa1159b4b8c7c4d69), but Dataverse OData queries expect standard GUID format (1a13663f-de2d-4a0f-a115-9b4b8c7c4d69).Changes
Added
Format_Flow_GUIDaction atInventory_this_flowscope that normalizes GUIDs to standard format if hyphens are missingUpdated 5 Dataverse actions to use
@outputs('Format_Flow_GUID')instead of@triggerBody()['text_2']forrecordIdparameters:See_if_flow_exists_to_mark_deletedFlow_existed_so_mark_deletedGet_Flow_from_InventoryUpsert_Flow_record_(creator_not_found)Upsert_Flow_recordDocumentation: Added fix guide and updated troubleshooting documentation
Compatibility
Backward compatible - handles both hyphenated and non-hyphenated GUIDs. No changes required to calling flows or existing data.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.