-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy new Power BI tmdl model #326
Comments
Sounds like the database.compatibilityLevel isn't set (or not to the right level). Could you check? |
If the issue is related to field params, it's likely that the problem is related to CompatibilityMode (not Level). Are you using an outdated version of pbi-tools? The latest versions should be setting the mode correctly. I distinctly remember fixing that. |
The compatibilityMode gets removed on save by Power BI. Therefor I would need to write a script to include it on every pipeline run. That is ok. but if you say it should be inherently set by pbi-tools then maybe something else goes wrong. I'm using ghcr.io/pbi-tools/pbi-tools-core:latest |
That's useful to know. It should work without any further external intervention. Will raise it with the team internally. You have a workaround for now, though. |
It's interesting, when you add the compatibilityMode: powerBI I still get an error which i'm not understanding at this point: |
Assign a name to both, the Database and the Model, object. That should fix this problem and is a known issue. |
Awesome, thank you very much for the explanation. |
I've converted my Power BI model to the new tmdl using Power BI Desktop. When trying to deploy this using pbi-tools I'm getting a compatibilityViolationException. In my model i'm using the field parameters and on this one the deploy seems to be breaking.
Below is the error message:
Microsoft.AnalysisServices.Tabular.CompatibilityViolationException: The usage of [model 'Model'].[table '.Self-Service Dimensions (IB - Data)'].[related column details] is not supported at AnalysisServices mode.
at Microsoft.AnalysisServices.Tabular.Database.SerializeToJsonObject(JsonObject result, SerializeOptions options)
at Microsoft.AnalysisServices.Tabular.Database.SerializeToNewJsonObject(SerializeOptions options)
at Microsoft.AnalysisServices.Tabular.JsonSerializer.SerializeDatabase(Database database, SerializeOptions options)
at PbiTools.Serialization.TabularModelSerializer.DeserializeTmdl() in X:\pbi-tools\BRANCHES\rc.8\src\PBI-Tools\Serialization\TabularModelSerializer.cs:line 565
at PbiTools.Serialization.TabularModelSerializer.TryDeserialize(JObject& database) in X:\pbi-tools\BRANCHES\rc.8\src\PBI-Tools\Serialization\TabularModelSerializer.cs:line 493
at PbiTools.Serialization.PowerBIPartSerializerExtensions.DeserializeSafe[T](IPowerBIPartSerializer`1 serializer, Boolean isOptional) in X:\pbi-tools\BRANCHES\rc.8\src\PBI-Tools\Serialization\IPowerBIPartSerializer.cs:line 41
I'm not sure what i need to do to make sure that this is not a problem anymore.
The text was updated successfully, but these errors were encountered: