Forum Discussion
Bug: Deployment Pipelines scramble GraphQL composite join conditions by re-sorting columns
Description:
I have identified a bug in the API for GraphQL where deploying via Fabric Pipelines changes the logic of composite relationships.
The Issue:
The deployment process appears to alphabetically sort the columns in the join condition. This breaks relationships where the alphabetical order of the Source columns does not match the alphabetical order of the Target columns.
Example:
Dev (Working):
Source Table: (ContractID, SapTenant)
Target Table: (MEM_VERTRAG, MEM_MANDT)
Note: ContractID maps to MEM_VERTRAG.
Test (Broken after Deployment):
The pipeline deploys the item, but sorts the join definition.
Resulting mapping: ContractID -> MEM_MANDT and SapTenant -> MEM_VERTRAG.
Cause: ContractID is alphanumerically first on the left; MEM_MANDT is alphanumerically first on the right.
Impact:
Silent Failure: The deployment succeeds without errors, but the API returns empty results in the target workspace because the keys are mismatched.
Drift: Manually fixing the relationship in the target workspace works temporarily, but the next deployment overwrites the fix, reverting it to the broken, sorted order.
Current Workaround:
We are forced to rename columns in our database views so that the alphabetical order aligns on both sides of the join, which is not a sustainable solution.
Hello Madrawn
Fabric’s source control and deployment for the GraphQL API are specifically classified as preview features. As is typical with preview releases, metadata may be serialised deterministically, such as sorting arrays to enhance diff stability, which may result in fields being reordered during deployment. It is important to note that Microsoft’s documentation does not specify any sorting behaviour, but it does confirm that Git and deployment pipelines are supported for the API in its preview phase.
I would advise submitting a ticket in support.fabric.microsoft.com for Microsoft to get this looked at and resolved at the earliest.
3 Replies
Hello Madrawn
Fabric’s source control and deployment for the GraphQL API are specifically classified as preview features. As is typical with preview releases, metadata may be serialised deterministically, such as sorting arrays to enhance diff stability, which may result in fields being reordered during deployment. It is important to note that Microsoft’s documentation does not specify any sorting behaviour, but it does confirm that Git and deployment pipelines are supported for the API in its preview phase.
I would advise submitting a ticket in support.fabric.microsoft.com for Microsoft to get this looked at and resolved at the earliest.
Hi Madrawn,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to deborshi_nag, for those inputs on this thread.Has your issue been resolved? If the response provided by the community member deborshi_nag, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.Hi Madrawn,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.Thank you.
