Passing view creation queries through git

[PedroCSeq]

Hey Everyone!
As you probably know, saved and shared queries are not presisted when comminting to or pulling from a git repo. This is posing a problem, as me and my team are all developing powerBI reports in our individual workspaces and all need to have the same views from our CURATED Lakehouse. All of us pointing to a single lakehouse/analytics endpoint is not feasable. Stored procedures are also not included in git commits/pull's so that method is also not appropriate. Creating the views using notebooks also ins't satisfying our requeriments, as they're not available when trying to include them in a semantic model and don't show up in the analytics endpoint as views in any of the folders (although just altering the word 'view' to 'table' in the creation query and the actual table is visible in the analytics endpoint). Is this an actual limitation of fabric and it's git integration? Is it not normal that the views don't show up in the endpoint? Is there any currently functioning method to use git to propagate the views/view criation queries to other environments(workspaces)?

[Anonymous · Accepted solution]

HI @PedroCSeq,

Here is the list of items that support with git integrations, you can check it if helps:

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Perhaps you can try to use 'attach it to the default semantic model' option and this will attached view to the lakehouse default semantic model as table. After these steps, you can simply use this in your worksapce.

Regards,

Xiaoxin Sheng

[Anonymous · Accepted solution]

HI @PedroCSeq,

Here is the list of items that support with git integrations, you can check it if helps:

Overview of Fabric Git integration - Microsoft Fabric | Microsoft Learn

Perhaps you can try to use 'attach it to the default semantic model' option and this will attached view to the lakehouse default semantic model as table. After these steps, you can simply use this in your worksapce.

Regards,

Xiaoxin Sheng

[KevinChant · Accepted solution]

, the views you create for a Lakehouse uses Spark SQL so they won't show up in the SQL endpoint. Only the Delta tables will like you mentioned in your workaround.

If you really want T-SQL views, you will have to create a Data Warehouse and create views in there using T-SQL that query your Delta Tables. Like in the below example:

Data warehouse tutorial - Create queries cross-warehouse with the SQL query editor - Microsoft Fabri...