Hi Support,
Hi Pratap. I have a question. Why does a warning message appears in the new release, for setting global variables when you declare them in definitions? This shouldn’t cause ambiguity on memory location when variables are consumed in DAX. Proof of this is shown in filter or lookup expressions when associated errors are thrown when data types are mismatched.
This error handling induces major costs for revisions of the app.

Report
All responses (
Answers (