docs: Note on naming of extra columns for date hierarchies in DAX API

Author: igorlukanin

docs/pages/product/apis-integrations/dax-api.mdx

@@ -43,9 +43,16 @@ To enable or disable the DAX API on a specific deployment, go to <Btn>Settings</
 in the Cube Cloud sidebar, then <Btn>Configuration</Btn>, and then toggle the
 <Btn>Enable DAX API</Btn> option.
 
-By default, the DAX API exposes all [time dimensions][ref-time-dimensions] as calendar
-hierarchies. You can set the `CUBEJS_DAX_CREATE_DATE_HIERARCHIES` environment
-variable to `false` to disable this behavior.
+### Date hierarchies
+
+By default, the DAX API exposes all [time dimensions][ref-time-dimensions] as _date
+hierarchies_ in [Power BI][ref-power-bi]. You can set the `CUBEJS_DAX_CREATE_DATE_HIERARCHIES`
+environment variable to `false` to disable this behavior.
+
+Note that each date hierarchy will include additional columns, suffixed by `_year`,
+`_quarter`, `_month`, `_day`. If the data model has other members with names that follow
+this pattern (e.g., a time dimension named `date` and another dimension named `date_year`
+in the same cube or view), that would cause a conflict.
 
 ## Authentication
 
@@ -72,4 +79,4 @@ The DAX API only exposes [views][ref-views], not cubes.
 [ref-time-dimensions]: /product/data-modeling/concepts#time-dimensions
 [ref-kerberos]: /product/auth/methods/kerberos
 [ref-ntlm]: /product/auth/methods/ntlm
-[ref-power-bi]: /product/configuration/visualization-tools/powerbi#connecting-from-power-bi
+[ref-power-bi]: /product/configuration/visualization-tools/powerbi

docs/pages/product/data-modeling/syntax.mdx

@@ -80,6 +80,7 @@ Common rules apply to names of entities within the data model. All names must:
 - Start with a letter.
 - Consist of letters, numbers, and underscore (`_`) symbols only.
 - Not be a [reserved keyword in Python][link-python-reserved-words], e.g., `from`, `return`, or `yield`.
+- When using the DAX API, not clash with the names of columns in [date hierarchies][ref-dax-api-date-hierarchies].
 
 It is also recommended that names use [snake case][wiki-snake-case].
 
@@ -777,4 +778,5 @@ defining dynamic data models.
 [ref-polymorphism]: /product/data-modeling/concepts/polymorphic-cubes
 [ref-data-blending]: /product/data-modeling/concepts/data-blending
 [link-js-template-literals]: https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Scripting/Strings#embedding_javascript
-[link-python-reserved-words]: https://docs.python.org/3/reference/lexical_analysis.html#keywords
+[link-python-reserved-words]: https://docs.python.org/3/reference/lexical_analysis.html#keywords
+[ref-dax-api-date-hierarchies]: /product/apis-integrations/dax-api#date-hierarchies

docs/pages/reference/data-model/types-and-formats.mdx

@@ -576,12 +576,6 @@ In order to be able to work with time series data, Cube needs to identify
 a time dimension which is a timestamp column in your database. You can define
 several time dimensions in a single cube.
 
-Note that the type of the target column should be `TIMESTAMP`. 
-If your time-based column is type `DATE` or another temporal type, 
-you should cast it to a timestamp in the `sql` parameter of the dimension. Please see
-[this recipe][ref-string-time-dims] if your datetime information is stored
-as a string.
-
 <CodeTabs>
 
 ```javascript
@@ -610,6 +604,17 @@ cubes:
 
 </CodeTabs>
 
+Note that the type of the target column should be `TIMESTAMP`. 
+If your time-based column is type `DATE` or another temporal type, 
+you should cast it to a timestamp in the `sql` parameter of the dimension.
+
+<ReferenceBox>
+
+Please see [this recipe][ref-string-time-dims] if your datetime information is stored
+as a string.
+
+</ReferenceBox>
+
 ### `string`
 
 `string` is typically used with fields that contain letters or special