DAX UDFs

[EvaluationContext]

Get alot of Unexpected Tuple errors when defining DAX User Defined Functions (UDFs) parameters, and => unexpected.

Example code here:

https://github.com/EvaluationContext/daxlib/blob/daxlib.svg/v0.1.2-beta/packages/d/daxlib.svg/0.1.2-beta/lib/functions.tmdl

[muhssamy]

i have the same issue also

[ggongg]

Thanks for providing your feedback! The dev team is investigating the issue and we will send more updates once we have them.

[ggongg]

Hi @EvaluationContext thanks again for creating this issue. The team has investigated and pushed a fix which will be part of the next release (expected around next week) so we would recommend checking with the newest version of the app once the new release comes out.

[RuiRomano]

Seems related, but also reports issues when using UDF functions in DAX measures:

[ggongg]

Hi @EvaluationContext @RuiRomano the updated release is now available, please let us know if you are still facing the same issue after updating. Thanks!

[EvaluationContext]

Looked today and is better but still get ... is not a function:

• ISNUMERIC()
• ISDATETIME()
• any UDF called in another UDF

[otykier]

Just tried 1.6.0, and it still shows an error when calling an UDF:

My functions.tmdl file looks like this:

[ggongg]

Hi @EvaluationContext, @otykier
Thank you for confirming the update and sharing the details. We’re glad to hear things are better, but we understand the remaining issue with UDF calls (e.g., ISNUMERIC(), ISDATETIME(), and nested UDF scenarios).
I will share this with the team. It appears related to how the extension parses user-defined functions within other functions, which is a known limitation. In the meantime, could you share:

The exact error message from the problems pane or screenshot you’re seeing (if not already included).

This will help us validate the fix against your scenario. We’ll keep you updated as soon as a patch or workaround is available.
Thanks for your patience and for helping us improve the extension!