search

TabularEditor / TabularEditor3

Bug reports, feature requests, discussion and documentation for Tabular Editor 3 (commercial version).
64 stars 7 forks source link

Delta Lake tables in Azure Data Lake Gen2 #403

Closed philip-charbonneau closed 2 years ago

philip-charbonneau commented 2 years ago

When pointing TE3 at a tabular model with delta lake tables (that use the connector from https://github.com/delta-io/connectors/tree/master/powerbi), addition/changes to the existing delta lake tables results in errors.

For example, if I try to create a copy of one of the tables, I get the error "the relationship for 'Variation' must be defined for the current table". If I try to enable the refresh policy on a table, I get the error "m engine error token literal expected".

As a work around, I make changes to the delta lake tables only in Power BI and any other changes are done with TE3.

Any suggestions on how I can get Delta Lake tables to work in TE3? Is there another connector I should be using?

Thank you.

otykier commented 2 years ago

Are you using auto date/time on your model? In general, models that use auto date/time tables do not work very well with TE3, since Power BI creates these hidden calendar tables for every DateTime column in the model. This is typically the cause of the "relationship for 'Variation' must be defined" error.

Regarding the refresh policy error, when exactly does that arise? It seems unrelated to the other error. Could you provide a step-by-step example on this?

philip-charbonneau commented 2 years ago

Thanks very much for the quick reply. You are correct, I had the model using the auto date/time tables. Once I removed them, the first error went away. The second error was due to an invalid setup of the incremental refresh policy. Everything is working great. Thanks again.