Forum Discussion
Renamed columns causing error
Hi,
We have a report the is pulled from SalesForce. One column in this report was previously named "Sales Rep." last week, we changed the wording to "Sales Representative" (only renamed it, did not create a new column.) I get the below error on my PBI reports that use this field now. I tried renaming the columns to "sales representative" but still receive the error. How do I get PBI to recognize the name column name without removing the data source altogether?
8 Replies
Based on your screenshot, the error occurs in Power BI Desktop. Do you create report in Power BI Desktop and publish the report to Power BI Service? If so, in Query Editor of Power BI Desktop, look into “APPLIED STEPS”, some steps should make changes/calculation on the ‘Sales Rep’ column(e.g. Change Type), you should delete such steps to solve the issue.
However, if you directly connect to SalesForce in Power BI Service, when you have schema changes(e.g. rename column) in the data source, you will receive the error like “The column ‘Sales Rep’ of the table wasn’t found”. You would need to remove the dataset in Power BI Service and re-connect to SalesForce.
Regards,
LydiaThat's really odd, renaming columns hasn't been an issue in Power BI for forever. Used to be really annoying. Where did you do the renaming, in Desktop or Query Editor? And you say that you tried renaming it back and it didn't fix the issue?
Hi,
To clarify, the renaming issue is stemming from a field that was renamed in Sales Force. It seems like pBI is still looking for the old name of the column. To resolve, I renamed the column in PBI (to match the new Sales Force field name). This was done on the desktop version (where the error was received). It did not work and is still searching for the old column name.
Hmmm. Yeah, I can see how that might be problematic. Are you able to trace back where the error is happening and perhaps change the formula? Distributed data governance is hard.
