Error during refresh only in PowerBI service and not on the desktop refresh

[lucadelicio]

Hi Everybody,

i need your help to find where is the error.

Sometimes during the refresh on PowerBI Service returns this error:
(Error data source:) Errore dell'origine dati: The '<oii>STRUTTURA_EMITTENTE</oii>' column does not exist in the rowset. Table: D_RICHIESTA_ACQUISTO.
Return the error only from the PowerBI service and not from the desktop.
But when i refresh from the desktop and i re-publish the error goes away.

There is a way to find where is used this column that the error returns?

What do you suggest. No measures are in error and i don't find nothing using this column.

Thank you very much every suggestion is appreciated.

[Anonymous]

Hi @lucadelicio,

I wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If the community member's answer your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.

Thank you,
Pavan.

[Anonymous]

Hi @Samrat_Ghosh_07,

I hope this information is provided by @SolomonovAnton  is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, kindly "Accept  as  Solution" and give it a 'Kudos' so others can find it easily.

Thank you,
Pavan.

[SolomonovAnton · Accepted solution]

🔍 Power BI Service vs. Desktop Refresh Error – Missing Column

You're encountering an issue where Power BI Service returns an error during dataset refresh:

Error: The '<oii>STRUTTURA_EMITTENTE</oii>' column does not exist in the rowset. Table: D_RICHIESTA_ACQUISTO.

This happens only in the Service, not in Desktop. Here's a breakdown of what could be happening and how to troubleshoot it effectively:

📌 Why the Discrepancy Happens

• Power BI Desktop uses your local credentials and connection string.
• Power BI Service uses a gateway (if applicable) or its own cloud credentials. Differences in data structure or timing can cause this.

🛠 Step-by-Step Troubleshooting

1. 🔎 Identify Where the Column is Used
   To find where STRUTTURA_EMITTENTE is used:
   • Open Power BI Desktop.
   • Go to Transform Data → Advanced Editor.
   • Search for STRUTTURA_EMITTENTE in all Power Query steps.
   • Also press Ctrl + F on the model to search all calculated columns, measures, and table filters.

   Alternative: Use DAX Studio with “View Metrics” to scan all expressions.

2. 🧪 Test Service Connection
   If a data gateway is involved:
   • In Power BI Service → Dataset Settings → Data source credentials: check for errors.
   • Make sure the gateway is connected to the same environment and DB schema.
   • Check if that column exists in the source system connected by the Service (DB view or stored procedure might be outdated).
3. 🔁 Check for Dynamic Schema Changes
   If the column appears/disappears intermittently:
   • It might be generated conditionally by a view/stored procedure.
   • Confirm with the database owner if column STRUTTURA_EMITTENTE is guaranteed to exist.
4. 💡 Use Power BI Helper Tool
   Power BI Helper lets you search where fields are used across visuals, queries, relationships, etc. It's great for detecting orphaned references.

✅ Recommendation

• Validate that all transformations using STRUTTURA_EMITTENTE are behind a Table.HasColumns check in Power Query, e.g.:

if Table.HasColumns(Source, "STRUTTURA_EMITTENTE") then
    Source[STRUTTURA_EMITTENTE]
else
    null

• Remove any unused columns explicitly if they aren't needed in your model.

📤 Final Tip

If republishing resolves the issue temporarily, you're likely seeing schema drift between refreshes. Consider scheduling refreshes only after confirming stability in the source structure.

---

✔️ If my message helped solve your issue, please mark it as Resolved!

👍 If it was helpful, consider giving it a Kudos!

[lucadelicio]

Thank you for the answer and all your tips. I'll try to find the error.

[Anonymous]

Hi @lucadelicio,

Thank you @SolomonovAnton  for the helpful respoinse.

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  as  Solution" and give a 'Kudos' so other members can easily find it.

Thank you,
Pavan.