key to any row of the table - dataflow source table is not visible to dataflow consumer

[trt18-sistemas]

Hi there,

I'm facing a problem to read a table located at dataflow origem, from a dataflow consumer. At the origin, the table is shown correctly (figure 1).

Figure 1 - Table UNIDADES at the origin.

But, at the destination dataflow, I can not see this table in order to import it (figure 2). 

Figure 2 - Table UNIDADES is not listed at "Get Data".

Anybody could say what's going wrong here and how can I solve this issue?

I have to say that I've just refreshed the dataflow source, but the problem persist.

Thanks in advance.

[trt18-sistemas · Accepted solution]

Solution came with Microsoft Support as described bellow.

At source dataflow some queries had "Replace error by null" steps inserted automatically by Power Query. After removing this step and refreshing the dataflow, it worked fine.

Just don't ask me why 😳

[Anonymous]

Hi,@trt18-sistemas

Regarding the issue you raised, my solution is as follows:
1.First of all, this is most likely due to a refresh delay, and sometimes, a delay in the refresh process can cause the form to not display immediately. Sometimes a delay in the refresh process may cause the table to not display immediately. Note that a Power BI Premium subscription is required to refresh more than 10 data streams in the workspace.The data stream refresh limit for Power BI Pro licenses is 8 refreshes per day. You can check if there are issues in your refresh history, if you are refreshing properly or if your configured scheduled refreshes are working correctly:

Here is the relevant documentation:
Understand and optimize dataflows refresh - Power BI | Microsoft Learn
Dataflows Limitations, restrictions and supported connectors and features - Power BI | Microsoft Lea...

2.Secondly, please check if the version of the dataflow and gateway are causing any impact. Make sure that both the source and target data flows are using Dataflow Gen2.The dataflow is now available in two versions, here is the difference between the two versions and how to migrate the query to the new version:

Differences between Dataflow Gen1 and Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Move queries from Dataflow Gen1 to Dataflow Gen2 - Microsoft Fabric | Microsoft Learn

This error occurs if the version of the local data gateway used to refresh the data stream (Gen1 or Gen2) is not supported. Currently, Microsoft supports only the six most recent versions of the Local Data Gateway. Update the gateway to the latest version or a supported version to resolve this issue. Below is the relevant documentation:

Currently supported monthly updates to the on-premises data gateways | Microsoft Learn

3.Finally, verify that you have the necessary permissions to access the table "UNIDADES" from the target data stream. Lack of appropriate permissions may result in the table not being displayed in the Get Data list.
Here is the relevant documentation:
Security roles and permission levels in standard dataflows - Power Query | Microsoft Learn

Best Regards,

Leroy Lu

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

[trt18-sistemas]

Hi @Anonymous ,

Thanks for your reply.

Solution 1 is not my case because the issue not only remains up to today as it's happening also at another workspace.
Solution 2 also doesn't apply as I'm using exclusively Dataflow Gen1 on my tenant. But, just in case, I've checked and both dataflows has the same purple dataflow icon, each means, they are from the same version.

Solution 3 also doesn't seems to be the case I'm working with Power BI environment only (not Power Platform), dataflows access are controled only by workspaces. Environment from Power Plataform doesn't apply to this case.

So, would you any other suggestion?

[Anonymous]

HI,@trt18-sistemas 

Thanks for the quick reply.

Have you solved the problem now?

If not, here are the solutions we can offer:

1.Since you are now experiencing inaccessibility of a single table in the dataflow,we would suggest you to try migrating the dataflow to gen2 version as per the requirement, here is the link for that:

Move queries from Dataflow Gen1 to Dataflow Gen2 - Microsoft Fabric | Microsoft Learn

2.Finally, you can also try to re-read the relevant data to see if this solves the problem.

If it has been resolved you are welcome to share your solution and accept your solution as a solution so that it is easy for other community members with the same issue to find a solution.

Best Regards,

Leroy Lu

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