Can't Save Dataflow

[learner03]

we use the query the table, it retrieves the data and when we save the table in the dataflow it throws this error message

Odbc.Query("dsn=GLOBALERP", "
    SELECT 
    ID Job_Status_ID,
    name as Job_Status
from JobStatus
  ")

[v-tsaipranay]

Hi @learner03 ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

[v-tsaipranay]

Hi @learner03 ,

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. 

Thank you.

[v-tsaipranay]

Hi @learner03 ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

[v-tsaipranay · Accepted solution]

Hi @learner03,

Thank you for reaching out to the Microsoft fabric community forum. 

The error message you’re seeing (“Can’t save dataflow – Unknown error”) usually appears when the ODBC connector isn’t fully set up in the Power BI Service.

While the ODBC connector is supported for Dataflows (see Microsoft documentation: ODBC connector), it must be configured through the On-premises Data Gateway. Make sure the DSN (GLOBALERP) is set up correctly on the gateway machine, mapped in the Service under Manage Gateways, and that the gateway is online.

Try running a simple query like SELECT TOP 1 * FROM JobStatus to check if the connector is working, and confirm that your query’s column names are unique and not reserved words, as duplicates can prevent the dataflow from saving.

If the issue persists, enable diagnostics in the Service and share your gateway configuration details for further investigation.

Hope this helps, feel free to reachout for any further questions.

Thank you.

[learner03]

@v-tsaipranay Sorry I saw the responses today, Usually I get an email when there is a response on the post but this time it didn't so I though no one has responded. Strangely, it automatically got fixed and I did nothing. Your response is correct but I already had many table that were using the same ODBC connection and I had faced no issue in the passed, so was finding it strange this time.

[v-tsaipranay]

Hi @learner03 ,

Thanks for confirming back. Glad to hear the issue has resolved on its own. Sometimes these “Unknown error” messages can occur due to transient gateway or service-side issues, which would explain why it started working again without any changes.