Data Warehouse Git

[Joshrodgers123]

I have git enabled in a workspace with a few data warehouses. Something in the backend keeps triggering changes to the 

xmla.json file that cause the workspace to show that there are uncommited changes. I am not making any changes to these warehouses, nor are any other uses. It seems that it is changes the PBI_QueryOrder and switching the order of the last 2 fields back and forth. 

When I commit the changes, they get switched back a few hours later and then it shows uncommited changes again. How do I get this to stop? 🙂

See below for the changes that keep occuring:

"name": "PBI_QueryOrder",

"value": "[\"base_kofax_ApproverNotes\",\"stg_kofax_ApproverNotes\",\"exec_requests_history\",\"long_running_queries\",\"frequently_run_queries\",\"exec_sessions_history\",\"dbo.base_kofax_ApproverNotes\"]"

"value": "[\"base_kofax_ApproverNotes\",\"stg_kofax_ApproverNotes\",\"exec_requests_history\",\"long_running_queries\",\"frequently_run_queries\",\"dbo.base_kofax_ApproverNotes\",\"exec_sessions_history\"]"

[mmilosanovic]

Hi all,

It seems that this was resolved and PBI_QueryOrder is no longer being source controlled in GIT.

Best regards,

Milos

[Anonymous]

HI @Joshrodgers123,

You can take a look at the following link about the sync and commit limits if they meet with your scenarios:
Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Regards,

Xiaoxin Sheng

[AndyDDC]

Hi @Joshrodgers123 ive actually reported this as an issue to MS Warehouse product team I've been having issues with Warehouses in Git. "Something" keeps on changing metadata unnecessarily and triggering an "uncommitted". I'll keep you posted, alternatively you can raise a support ticket yourself with all the details and MS can loook into further.

[Joshrodgers123]

Glad to hear its not just me! I also opened a support ticket (2408070040005034) to help hopefully push things along.

[Anonymous]

HI @Joshrodgers123,

Is there any update on this issue? It should be helpful to other users if you share detail information of issue progress here.

Regards,

Xiaoxin Sheng

[mmilosanovic]

@Anonymous any update? Thank you.

I also opened a support ticket: 2409130020000653

[mmilosanovic]

hi @Anonymous do you have any update on this issue? Thanks.

[Joshrodgers123 · Accepted solution]

It seems to have been resolved this week.

[AliKettani]

Hi. We have also the same issue here and we don't know yet how we can stop it. Please fix this.

Thanks

[mmilosanovic]

hi @Joshrodgers123 this still seems to be the issue. It just happened to me:

[Joshrodgers123]

You're right. Still happening to us as well. I let the support engineer know. 

[fahdsaleem]

Hi @Joshrodgers123 The same issue is happening in our environmnet. Any update. Is there a way to look into the ticket that you have opened with Fabric.

[Joshrodgers123]

Support stopped responding to me, so kinda gave up...

[mmilosanovic]

This is what I received from the support and all the proposals are too much of a workaround or they will not work in the real life. I suggested them to go with #5 from the list:

[fahdsaleem]

@Joshrodgers123 We are trying to branch out to a private workspace and then do pull request to get changes into main branch. The issue is that due to this PBI_QueryOrder issue Warehouse shows Conflict when synching changes from branch back into shared release workspace. The conflict is due to the fact that PBI_QueryOrder changed in workspace as well as branch from where we are getting it. Any recommendation.

[AndyDDC]

Great, thank you