This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
The only step in my deployment for test and production switching that is still unsupported are DirectLake semantic model sources. I have been successful in some hacky fixes where I can parameterize the directlake source but it then breaks editing of the directlake semantic models.
Specifically toggling the url in the semantic model expression:
expression 'DirectLake - kusa_accounting' =
let
Source = AzureStorage.DataLake("https://onelake.dfs.fabric.microsoft.com/workspaceid/lakehouseid", [HierarchicalNavigation=true])
in
Source
If we could usue a parameter here, normal Deployment Pipeline rules could change this. Better would be detecting this data source and allowing for setting the url in a data source pipeline rule would save having to create a parameter myself.
Alternatively, I'm using Variable Libraries in my other areas of deployment, and if we could specify this url from the Variable Libraries would work. This would probably be better since I find Variable Libraries more flexible and usable even without Fabric Deployment Pipelines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.