Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
PieterDL
Regular Visitor

Dataflow computed entity parameters "UnknownError"

Good day, I know with computed entities if you reference a dataflow from another dataflow you cannot refresh, but in this case I have 2 parameters that we use for our Server and Path connection in Databrics, currently I am getting weird error. Last week this was fine.

 

This works if I take out the parameters, but when I add them I get error

 

PieterDL_0-1719401326491.png

 

PieterDL_1-1719401413763.png

 

1 ACCEPTED SOLUTION
hackcrr
Super User
Super User

Hi, @PieterDL 

Encountering "Unable to save data stream: unknown error" in Power BI, especially when connecting with parameters in Databricks, is usually an indication of a problem with the way the parameters are handled or with the underlying service connection. Here are some steps to troubleshoot and resolve this issue:
Validate parameter values: Ensure that the parameter values for the sum are set correctly for Server and that the Path matches the expected format.
Test the connection without parameters: as you mentioned, the data flow works fine after removing the parameters. This confirms that the problem is with the parameters. Re-create the connection without parameters and verify connectivity to ensure there are no potential issues.
Check stream settings: Ensure that all settings and permissions for the stream are properly configured. This includes ensuring that the necessary gateways are set up and running (if required).
Re-create parameters: Try deleting and re-create the parameters in the data stream to see if this resolves the issue. There may be undetected corruption or misconfiguration in the current parameters.
Parameter Privacy Settings: Ensure that the privacy level settings for the data source are properly configured. Sometimes mismatched privacy levels can cause problems with parameters.
Check the M-code of the query in the data stream to make sure the parameter is referenced correctly. Example:

let
    Source = Databricks.Contents(Parameter_Server, Parameter_Path)
in
    Source

If the problem persists after following the steps above, consider implementing a workaround:
Hard-code the connection string: as an interim measure, hard-code the connection string into the data stream instead of using parameters.
Use Power BI Desktop:
Create the data stream in Power BI Desktop so that you have better control over the parameters and connections. Then publish the data stream to the Power BI service.

 

 

 

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly

View solution in original post

3 REPLIES 3
SaiTejaTalasila
Super User
Super User

Hi @PieterDL ,

 

Export json file of that dataflow and try to recreate one more dataflow and check whether you were able to save it or not.

 

Thanks,

Sai Teja 

hackcrr
Super User
Super User

Hi, @PieterDL 

Encountering "Unable to save data stream: unknown error" in Power BI, especially when connecting with parameters in Databricks, is usually an indication of a problem with the way the parameters are handled or with the underlying service connection. Here are some steps to troubleshoot and resolve this issue:
Validate parameter values: Ensure that the parameter values for the sum are set correctly for Server and that the Path matches the expected format.
Test the connection without parameters: as you mentioned, the data flow works fine after removing the parameters. This confirms that the problem is with the parameters. Re-create the connection without parameters and verify connectivity to ensure there are no potential issues.
Check stream settings: Ensure that all settings and permissions for the stream are properly configured. This includes ensuring that the necessary gateways are set up and running (if required).
Re-create parameters: Try deleting and re-create the parameters in the data stream to see if this resolves the issue. There may be undetected corruption or misconfiguration in the current parameters.
Parameter Privacy Settings: Ensure that the privacy level settings for the data source are properly configured. Sometimes mismatched privacy levels can cause problems with parameters.
Check the M-code of the query in the data stream to make sure the parameter is referenced correctly. Example:

let
    Source = Databricks.Contents(Parameter_Server, Parameter_Path)
in
    Source

If the problem persists after following the steps above, consider implementing a workaround:
Hard-code the connection string: as an interim measure, hard-code the connection string into the data stream instead of using parameters.
Use Power BI Desktop:
Create the data stream in Power BI Desktop so that you have better control over the parameters and connections. Then publish the data stream to the Power BI service.

 

 

 

If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly

Anonymous
Not applicable

Hi, @PieterDL 

You mentioned last week that this setup is working fine, so looking at any changes you've made to your Dataflow or Databricks environment since then will figure out why this error is occurring.
In addition, you can also check whether the current parameter settings are correct, including the case and parameter values.

 

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.