search

TabularEditor / TabularEditor3

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

Running into a limit with a long DAX expression in a C# script #145

Closed dpesante closed 3 years ago

dpesante commented 3 years ago

I have a TE3 script that is generating a very long DAX (approx 5000 lines long). The script runs end generates and error stating this:

"Expression: The end of the input was reached."

Was is strange is that when I save my changes it updates the measure and in Power BI and the measure is marked as an error but then if I open the measure in Power BI and just hit "enter" (no changes).. .Power BI compiles the measure without any errors.

Is there a limit to the number of characters the expression can be? Is there a way to get around this? After all, Power BI seems to allow it. I am attaching an example of the generated measure for you to review.

In my case I can not use an "Active" or "Inactive" join for reasons that I can explain if we get on the phone but regardless, I would have expected for TE3 to have at least the same limits that Power BI can handle in terms of the size of the expression.

I am also getting a timeout from the Model.AllMeasures.FormatDax(); because I have close to 20 measures this long. Is there a way for me to call the FormatDax for a single measure?

Thanks for your help on this. Please let me know if you have any questions.

dp long dax.docx

dpesante commented 3 years ago

Quick update... It turns out that I was missing 2 ")" at the end of the DAX expression. I had not noticed that the DAX Power BI editor, automatically added the 2 ")"'s for me which is why it accepted the DAX when all I did was to resend it. So, there is no bug in TE3 but just a difference in behaviour around completing and incomplete DAX as the Power BI DAX editor does.... We can close this issue. :-)