Forum Discussion
Error: column doesn't exist (but it does exist), cannot identify the error in desktop, only service
Hi RenateBK
Could you please try this:- Reorder or Rebuild Query Steps
Start from the Source step and rebuild the steps one-by-one. Try applying Changed Type after filtering rows instead of before — sometimes type detection introduces implicit transformations that block folding. - Check for Dynamic Metadata Columns
That column "<oii>>10 år</oii>" might have been part of a dynamic SharePoint view or metadata field that only appears under certain user contexts. If it was originally created or filtered by the deactivated user, the service may not be able to access it anymore.
Try this:
- In Power Query, go to View > Column quality/profiling, and check if that column exists when manually refreshing from SharePoint now.
- If it doesn’t, that’s likely the root of the error.
- Disable “Allow Data Preview to Download in the Background” (optional)
This can sometimes interfere with data shaping from SharePoint. Go to File > Options and settings > Options > Global > Data Load, and uncheck that setting as a test. - Isolate the Faulty Query
Since you mentioned testing a stripped-down version still throws the error, try duplicating the query, keeping only the Source step, and loading it to a blank report in a new PBIX. If that loads without errors, add the next steps one-by-one until the failure occurs again. This can help pinpoint the exact operation Power BI Service is choking on.
- Reorder or Rebuild Query Steps
Hi RenateBK
This kind of issue is surprisingly common when a report is handed over after someone's account is deactivated — especially with SharePoint as the source. Even though everything seems fine in Desktop, Power BI Service is stricter and sometimes throws errors for things that are silently tolerated locally.
That specific error about "<oii>>10 år</oii>" sounds like a column that was either renamed, removed, or perhaps dynamically created (like from a SharePoint view or metadata). Here's what I’d suggest:
- Open Power Query and go through each step in the affected table (Table_name (2)). One of them might still be referring to the old column even if it doesn’t show an error.
- Try refreshing the data manually in Desktop. Sometimes the issue only shows up during refresh, not on open.
- Also, check if that column is being used in a custom visual or a measure you mentioned a warning about custom visuals needing to be saved, which could be a clue.
- As a quick test, you can publish a copy of the report with just that table included. If the error still pops up, you’ll know that’s where the issue lies.
- Lastly, if this report uses parameters or dynamic SharePoint queries, try checking for broken paths or filters that may have depended on the previous user’s context.
Hello Rohit,
Thank you for the reply.
I have already tried publishing a test and the error still pops up in this table.
I also tried manually refreshing all the data in Desktop and experienced no error.
There has been no changes in the columns or editing.
When I'm looking at the semantic model in Service, the error message for the source says "This step will be evaluated outside the data source". However I cannot understand how to fix this due to how the report is set up.
(The steps are as following: Source, Changed Data type, then filtered rows)
Just to make you understand what type of semantic model it is that I have to try and work with here. I am planning on completely remaking it as this is breaking just about every best practice, however it is not something I can prioritise right now and if possible I would love to just be able to fix this somehow without having to do any major changes to the report.
Hi RenateBK
Could you please try this:- Reorder or Rebuild Query Steps
Start from the Source step and rebuild the steps one-by-one. Try applying Changed Type after filtering rows instead of before — sometimes type detection introduces implicit transformations that block folding. - Check for Dynamic Metadata Columns
That column "<oii>>10 år</oii>" might have been part of a dynamic SharePoint view or metadata field that only appears under certain user contexts. If it was originally created or filtered by the deactivated user, the service may not be able to access it anymore.
Try this:
- In Power Query, go to View > Column quality/profiling, and check if that column exists when manually refreshing from SharePoint now.
- If it doesn’t, that’s likely the root of the error.
- Disable “Allow Data Preview to Download in the Background” (optional)
This can sometimes interfere with data shaping from SharePoint. Go to File > Options and settings > Options > Global > Data Load, and uncheck that setting as a test. - Isolate the Faulty Query
Since you mentioned testing a stripped-down version still throws the error, try duplicating the query, keeping only the Source step, and loading it to a blank report in a new PBIX. If that loads without errors, add the next steps one-by-one until the failure occurs again. This can help pinpoint the exact operation Power BI Service is choking on.
- Reorder or Rebuild Query Steps
