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.
What is the error message? How did you create the Global and Context Variable? Please share the detailed configuration of the related formula. If possbile, also try to recreate the app to see if the error still shows.
Community Support Team _ Mona Li If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.