cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
j_w Member
Member

Is date_start a reserved keyword in DAX?

When I use date_start as a variable in DAX I get following error:

image.png

 

But if I rename date_start to date_start2 or date_sta, it is fine.

 

So why there is an error when I use date_start?

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support Team
Community Support Team

Re: Is date_start a reserved keyword in DAX?

Hi @j_w,

 

By confirmed by PG, due to historical reasons, DAX parser started as an extension to MDX parser therefore automatically inherited all the MDX keywords. Since MDX parser was limited back in the old days, all MDX functions and metadata properties were added as keywords which unfortunately included DATE_START.

 

As a good coding convention, I recommend users to always prefix DAX variables with v or some other prefix the user prefers. So instead of DATE_START, the user could use vDateStart to make his code easy to read and maintain and also avoid accidental keyword collisions.

 

Best Regards,

Cherry

Community Support Team _ Cherry Gao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 REPLIES 2
Community Support Team
Community Support Team

Re: Is date_start a reserved keyword in DAX?

Hi @j_w,

 

I have had a contact with PG and will update here if I get any information.

 

Sorry for any inconvenience.

 

Best  Regards,

Cherry

Community Support Team _ Cherry Gao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Community Support Team
Community Support Team

Re: Is date_start a reserved keyword in DAX?

Hi @j_w,

 

By confirmed by PG, due to historical reasons, DAX parser started as an extension to MDX parser therefore automatically inherited all the MDX keywords. Since MDX parser was limited back in the old days, all MDX functions and metadata properties were added as keywords which unfortunately included DATE_START.

 

As a good coding convention, I recommend users to always prefix DAX variables with v or some other prefix the user prefers. So instead of DATE_START, the user could use vDateStart to make his code easy to read and maintain and also avoid accidental keyword collisions.

 

Best Regards,

Cherry

Community Support Team _ Cherry Gao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.