Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
The new Data Agent cannot handle space bars from Power BI Datasets i.e. if it's trying to access 'Created Date' it will call it 'Created_Date' in the DAX/SQL and fail, I have tried to implement an instruction to tell it not to do so. Is there an easier fix than having to go through every dataset I want to use with the Data Agent and removing the spaces, and brackets etc.?
Solved! Go to Solution.
Hi @willfleming,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The issue arises because the Data Agent auto converts column and table names with spaces (e.g., 'Created Date') into formats like 'Created_Date', causing failures when accessing Power BI datasets. Instead of manually renaming each field, easier workarounds include wrapping column names with spaces in square brackets in queries, creating SQL views or Power BI Dataflows with Data-Agent-friendly column names, configuring the Data Agent (if possible) to preserve original names, or using internal field names like 'Created_Date' while setting display names as 'Created Date' in Power BI. These approaches help maintain readability without breaking compatibility.
If you find this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to support others in the community.
Thank you & regards,
Prasanna Kumar
Hi @willfleming,
Just a gentle reminder has your issue been resolved? If so, we’d be grateful if you could mark the solution that worked as Accepted Solution, or feel free to share your own if you found a different fix.
This not only closes the loop on your query but also helps others in the community solve similar issues faster.
Thank you for your time and feedback!
Best,
Prasanna Kumar
Hi @willfleming,
We wanted to kindly check in to see if everything is working as expected after trying the suggested solution. If there’s anything else we can assist with, please don’t hesitate to ask.
If the issue is resolved, we’d appreciate it if you could mark the helpful reply as Accepted Solution — it helps others who might face a similar issue.
Warm regards,
Prasanna Kumar
Hi @willfleming,
Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.
If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful — this will benefit others in the community as well.
Best regards,
Prasanna Kumar
Hi @willfleming,
Thank you for reaching out to the Microsoft Fabric Forum Community.
The issue arises because the Data Agent auto converts column and table names with spaces (e.g., 'Created Date') into formats like 'Created_Date', causing failures when accessing Power BI datasets. Instead of manually renaming each field, easier workarounds include wrapping column names with spaces in square brackets in queries, creating SQL views or Power BI Dataflows with Data-Agent-friendly column names, configuring the Data Agent (if possible) to preserve original names, or using internal field names like 'Created_Date' while setting display names as 'Created Date' in Power BI. These approaches help maintain readability without breaking compatibility.
If you find this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to support others in the community.
Thank you & regards,
Prasanna Kumar
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.