Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreShape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.
I am trying to move my pbix model to a VS project in order to have some functionality that is missing in PBI Desktop. However, the compatability level available on SSAS is currently 1500 compared to 1520 on PBI Desktop. Versions of servers are different as well with the latest for SSAS being 15.0.18333.0 and on PBI Desktop being 15.1.40.25. If I try replacing a VS model.bim file and try to open in I get errors as some settings are not available. Is there to be an updated template for VS or an equivalent release for SSAS that is the same as PBI Desktop. Any suggestions would be useful.
Hello, I'm refreshing this topic to ask if anything in above subject has changed?
Can we somehow deploy "defaultPowerBIDataSourceVersion": "powerBI_V3" to Analysis Services?
Hi @OlapOffice ,
take a look at the tabular editor
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
I did. I opened the PowerBI model in Tabular Editor and then saved to Model.bim file and replaced the VS model.bim file. This is where there is a difference in Compatability and settings in the later version than available through VS.
I would have tried to deploy the model from the tabular editor to the tabular SSAS instance first.
PBIT -> SSAS Tabular -> VS
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
Thanks for the suggestion. I get the error below.
---------------------------
Error occured during deployment
---------------------------
The JSON DDL request failed with the following error: Unrecognized JSON property: sourceQueryCulture. Check path 'model.sourceQueryCulture', line 14, position 30..
---------------------------
OK
---------------------------
{
"create": {
"database": {
"name": "TEST",
"compatibilityLevel": 1520,
"model": {
"culture": "en-US",
"dataAccessOptions": {
"legacyRedirects": true,
"returnErrorValuesAsNull": true,
"fastCombine": true
},
"defaultPowerBIDataSourceVersion": "powerBI_V3",
"sourceQueryCulture": "en-US",
"tables": [
{
Hi @OlapOffice ,
maybe activating this setting will help.
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
Unfortunately that did not work. I have tried different combinations to no avail.
Hi @OlapOffice ,
maybe they can be helped directly here.
https://github.com/otykier/TabularEditor/issues/163
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
Thanks for all your help. I will try there.
Hi I have moved Power BI model, to SSMS, and I am now trying to run the JSON DDL script and I am getting exactly the same error "The JSON DDL request failed with the following error: Unrecognized JSON property: sourceQueryCulture. Check path 'model.sourceQueryCulture', line 14, position 30.." - have you solved this yet and how
I am running the DDL in SSMS, against SSAS instance, not in VS, so I dont think I have a Tabular editor there
Hi @Anonymous ,
have you already read and tried this?
"Thank you for your quick respond,
I did that.
I edited JSON file and I changed Compatibility Level to 1400 and then I saved it.
but when I wanted to deploy this BIM file on the SSAS server an error occurred
"Failed to execute XMLA. Error returned: 'The operation cannot be performed because it references an object or property that is unavailable in the current edition of the server or the compatibility level of the database."
but I tried another way and it worked. I don't like this way but it works 🙂
I generate the database script and then I changed Compatibility Level to 1400 in JSON file and the database name. I created new database with new Compatibility Level by executing that query."
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
I guess "defaultPowerBIDataSourceVersion": "powerBI_V3", is to new for 1400?
Hi, i just tried that and now I get this
"The JSON DDL request failed with the following error: Unrecognized JSON property: defaultPowerBIDataSourceVersion. Check path 'model.defaultPowerBIDataSourceVersion', line 12, position 43.."
my property is this "defaultPowerBIDataSourceVersion": "powerBI_V3",
Hi @Anonymous ,
I found this one and I am afraid that the PBI data model (Power BI Desktop >= March 2020) is too current for the SSAS Tabular Server.
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
I have had a read through this, can it only be done with power bi premiuim? I dont have that. Maybe I could download and older version of Power BI, load my pbix into that?
You are welcome.
Please give Kudos for support.
Marcus Wegener works as Full Stack Power BI Engineer at BI or DIE.
His mission is clear: "Get the most out of data, with Power BI."
twitter - LinkedIn - YouTube - website - podcast - Power BI Tutorials
I am running the DDL in SSMS, against SSAS instance, not in VS, so I dont think I have a Tabular editor there
Hi I have moved Power BI model, to SSMS, and I am now trying to run the JSON DDL script and I am getting exactly the same error "The JSON DDL request failed with the following error: Unrecognized JSON property: sourceQueryCulture. Check path 'model.sourceQueryCulture', line 14, position 30.." - have you solved this yet and how
User | Count |
---|---|
90 | |
88 | |
87 | |
79 | |
49 |
User | Count |
---|---|
153 | |
145 | |
106 | |
74 | |
55 |