Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Error message
<ccon>Expression.Error: The column 'Numbering Posts' of the table wasn't found.. Numbering Posts. </ccon>. The exception was raised by the IDbCommand interface. Table: Leadership Calendar.
I already deleted this in the Model in the Service (web), but still getting an error. Looks like I have to redo the source in the app. Is there a way to fix this in the Service without downloading the PBIX?
Solved! Go to Solution.
Hi @New_Folder
It sounds like the error is related to the column 'Numbering Posts' in the Leadership Calendar table, which is no longer present in your model in the Power BI Service, but there’s still some reference to it causing the issue. To resolve this without downloading the PBIX file, try the following steps:
Go to the Power BI Service and navigate to the dataset that’s causing the issue.
Open the dataset settings and click on "Schedule Refresh" to verify if there’s any cached data or old settings that may be referencing the column.
Check Data Source Credentials to ensure there’s no outdated information that’s causing the error during data refresh.
Clear the cache or rebuild the data model within the Service if the issue persists. This can be done by refreshing the dataset, and Power BI Service will try to re-evaluate the model.
If none of these steps resolve the issue, and the column is still not found even after clearing, it might be necessary to go to the original report in the Desktop application (PBIX), remove any references to the column explicitly from queries or relationships, then re-publish.
If the error is persistent, trying to fix it without downloading the PBIX is difficult, as you may need to fully re-check your model structure and references in the desktop version.
Hi @New_Folder ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @New_Folder
It sounds like the error is related to the column 'Numbering Posts' in the Leadership Calendar table, which is no longer present in your model in the Power BI Service, but there’s still some reference to it causing the issue. To resolve this without downloading the PBIX file, try the following steps:
Go to the Power BI Service and navigate to the dataset that’s causing the issue.
Open the dataset settings and click on "Schedule Refresh" to verify if there’s any cached data or old settings that may be referencing the column.
Check Data Source Credentials to ensure there’s no outdated information that’s causing the error during data refresh.
Clear the cache or rebuild the data model within the Service if the issue persists. This can be done by refreshing the dataset, and Power BI Service will try to re-evaluate the model.
If none of these steps resolve the issue, and the column is still not found even after clearing, it might be necessary to go to the original report in the Desktop application (PBIX), remove any references to the column explicitly from queries or relationships, then re-publish.
If the error is persistent, trying to fix it without downloading the PBIX is difficult, as you may need to fully re-check your model structure and references in the desktop version.
Hi @New_Folder ,
Thank you for posting in the Microsoft Fabric Community. Also thank you @Akash_Varuna for your inputs.
The error you're seeing, the column 'Numbering Posts' of the table wasn't found usually occurs when a deleted column is still being referenced in visuals, measures, or query steps. Even though you’ve removed the column from the model in the Power BI Service, those references can still exist and cause the issue.
To resolve this directly in the Power BI Service without downloading the PBIX, open the report in Edit mode and check all visuals and fields for any remaining references to 'Numbering Posts'. Also, use Transform data to access Power Query Online and review the applied steps and remove or update any that reference the deleted column. After making these changes, refresh the dataset to clear the error. If the issue persists, modifying the report in Power BI Desktop and republishing may be necessary.
For guidance, you can refer to these official Microsoft resources:
The Power Query user interface - Power Query | Microsoft Learn
What is Power Query? - Power Query | Microsoft Learn
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi @New_Folder ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @New_Folder The error is showing that the dataset still references a deleted column. If it's a PBIX upload, you'll need to fix it in Desktop and re-upload. If it's a dataflow or semantic model, check and remove the column in the Service.
Anyway we can update when a column is modified (we are using smartsheet), without using desktop?
Hi @New_Folder ,
Currently, Power BI does not auto-detect or adapt to schema changes like renamed or deleted columns from Smartsheet within the Service. While you can use Transform Data in the Service to fix broken steps manually, structural changes in the source (like column updates) typically require you to update the PBIX in Power BI Desktop and re-publish. There’s no Service-only workaround for schema sync at this time.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi @New_Folder ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!