Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
In Power BI Service (no Desktop), when I create a calculated column, the editor often auto‑appends .[Date] after my date column reference, turning\ MDR[Planned Submittal Date] into MDR[Planned Submittal Date].[Date].\ This then throws “The syntax for ‘;’ is incorrect.” Removing .[Date] and typing the tail manually fixes it. Looking for a way to prevent the append or disable the behavior in Service.
Environment
Goal\ Calculated column for KPI v1 (On‑Time Submission):
OnTime Flag = IF( MDR[Actual submission date] <= MDR[Planned Submittal Date]; 1; 0 )
Problem / Error\ Editor auto‑completes to:
MDR[Planned Submittal Date].[Date]
Then DAX fails with:
The syntax for ‘;’ is incorrect.
Repro steps
Workarounds I’ve used (work but clunky)
Questions to the community
Thanks
Solved! Go to Solution.
Hi @SamHE ,
Thanks for reaching out to Microsoft Fabric Community.
Thanks for the detailed repro and for documenting the behavior clearly.
The guidance shared earlier by @lbendlin about disabling Auto Date/Time is correct when the model is authored or modified using Power BI Desktop, as that setting is only available there.
For models created and edited only in Power BI Service, there is currently no editor setting available to stop the auto insert of hierarchy members such as .[Date] while keeping IntelliSense enabled. This behavior is a limitation of the Service DAX editor.
Auto date/time in Power BI Desktop - Power BI | Microsoft Learn
From a best practices perspective, when authoring models or calculated columns in Service:
->Prefer explicit date columns or a dedicated date table rather than relying on implicit date hierarchies
->Keep date comparisons simple and explicit to avoid hierarchy member insertion
->Use consistent patterns for calculated columns to reduce editor side rewrites
Given this limitation, the workarounds you listed, such as using a VAR based pattern or confirming the column reference ends at ], are the recommended approaches for handling this behavior when authoring calculated columns directly in the Service.
Thanks for sharing those workarounds along with the repro steps.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @SamHE ,
Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.
Thank you.
Hi @SamHE ,
Thanks for reaching out to Microsoft Fabric Community.
Thanks for the detailed repro and for documenting the behavior clearly.
The guidance shared earlier by @lbendlin about disabling Auto Date/Time is correct when the model is authored or modified using Power BI Desktop, as that setting is only available there.
For models created and edited only in Power BI Service, there is currently no editor setting available to stop the auto insert of hierarchy members such as .[Date] while keeping IntelliSense enabled. This behavior is a limitation of the Service DAX editor.
Auto date/time in Power BI Desktop - Power BI | Microsoft Learn
From a best practices perspective, when authoring models or calculated columns in Service:
->Prefer explicit date columns or a dedicated date table rather than relying on implicit date hierarchies
->Keep date comparisons simple and explicit to avoid hierarchy member insertion
->Use consistent patterns for calculated columns to reduce editor side rewrites
Given this limitation, the workarounds you listed, such as using a VAR based pattern or confirming the column reference ends at ], are the recommended approaches for handling this behavior when authoring calculated columns directly in the Service.
Thanks for sharing those workarounds along with the repro steps.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @SamHE ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.
In the options and settings/ options dialog disable the Auto Date/Time setting both for the report and globally.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |