Fix SYNC HELPER - Cloud Flows parse failures on null connection properties #10643
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 was failing when inventorying flows with connection references containing null
id,connectionName, ordisplayNameproperties—common in Default Environments with embedded or system connections.Changes
id,connectionName, anddisplayNamefieldsrequired: ["id"]constraint that blocked null ID processingTechnical Details
Modified the JSON schema in the flow definition to accept both string and null types:
This allows the flow to process connection references regardless of whether metadata properties are populated, preventing "Invalid type. Expected String but got Null" errors during inventory operations.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.