TOM property not deployed to Semantic model (dataCoverageDefinition) - Hybrid table setup
I'm trying to deploy a property dataCoverageDefinition in my semantic model's partition.
I need this for a hybrid model setup, where one partition is set to direct query, and the other one to Import.
According to the documentation, an additional property needs to be deployed to the directquery partition to make sure Power BI does not perform any unnecessary queries in direct query mode.
Compatibility has been set to 1604.
Property has been set into the DirectQuery partition.
Script runs succesfully, but the property cannot be found when re-opening the script of the datamodel.
When reviewing the performance analyzer, Power BI still performs unnecessary direct queries when the requested data is clearly data stored in the import partition.
8 Comments
Hi HSpeelman ,
It seems like you’re doing everything correctly according to the documentation. The property should indeed provide a hint regarding the data that is covered by the partitionDataCoverageDefinition. This property is supported when the compatibility level of the database is at 1603 or above, which is the case in your situation (1604).
However, if the property is not found when re-opening the script of the data model, it might be due to some issues with the deployment process. You could try using the Deployment Wizard for deploying model solutions. It uses JSON output files generated from an SQL Server Analysis Services project as input files, which are easily modifiable to customize the deployment.
You may refer to Deploy model solutions by using the Deployment Wizard | Microsoft Learn
Best regards.
Community Support Team_CaitlynHi v-xiaoyan-msft,
We are currently not using SSAS, but Power BI premium capacity. When opening the Deployment Wizard I see no option to connect to the premium workspace. We don't have an '.asdatabase' file which is needed for this tool. Do you have any other suggestions or tools that can deploy an xmla file to a power bi premium workspace?
Thanks in advance.
Henny
dmkblesserAdvocate II
I'm running into the exact same situation. Followed the same document as the OP posted. adding dataCoverageDefinition and execute successfully, however, after a refresh of the table, the property `dataCoverageDefinition` just vanished, and based on the performance of the report, the property did not get added successfully.- dmkblesser, I logged the bug with Tabular Editor (as I read you could implement it there as well). And they fixed it straight away. Make sure you download the latest version. I’m still not sure if the issue persists with SSMS. Hope it helps.
- dmkblesserHi @HSeelman, Thank you so much for your response. yeah I deployed using SSMS and I could tell it was still not working with SSMS. I have TE 2 and I will give it a shot. Thanks again for the heads up!
- dmkblesserHi HSpeelman. Probably it was not supported by TE2? Do you mind if you can tell me whether you are using Tabular Editor 3 and where did you add the property? i can create two partitions in my TE2 but they are not in the same json format as how the document showed https://learn.microsoft.com/en-us/analysis-services/tom/table-partitions?view=asallproducts-allversions, and I'm not sure where to add this property. Appreciate any information you can share!
- Hi dmkblesser, The property is available in TE2. (I used TE2). First you need to set the compatibility mode of your semantic model (I think 1604). You can do this via altering the value when you click on the model name at the left hand side of the UI. Then after you create the partitions, you have a new option called 'datacoveragedefinition' where you can put in the DAX you need for the filter. (in the link there is a screenshot of the property) https://github.com/TabularEditor/TabularEditor/issues/1190 I hope this helps! Cheers, Henny
- dmkblesserHi Henny, thank you so much for the information. I'm able to make it work with Tabular Editor now! Just one quick question, I ran across your old ticket https://github.com/TabularEditor/TabularEditor/issues/1186. I see that in your set up, you have the dataCoverageDefinition on the fact table: 'FactTable'[Date Key] < 20230101. Did you end up with the same setup and got it working? I contacted Microsoft support and basically they told me that `<` will only work on the dual mode table which will be the dimensional table based on the document Originally, I had it the same setup as what you have done. I have to add the dimensional table (I don't have a dimensional table originally since it is a poc), and then it worked for me.
