We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
I am trying to capture the current query in the #sections table in Power Query.
The current query generates a circular dependency, so I tried using try [Value] otherwise null and several other ways to check which record in the seciton table generated the error. It e.g. captures the HasError value correcty (HasError = True), while others are false.
However, when trying to retrieve the value for HasError, it does not retain the TRUE value, likely due to the underlying table not having errors. Similarly when trying to get the record fieldnames and expanding them, and so on. I also tried to retrieve the error message via a range of other means.
Does anyone have any idea how to retrieve this in power query?
Solved! Go to Solution.
I found an alternative route to achieve what I tried to achieve, so getting the error is no longer needed. I generated a uniquer tableid and compared that with the nested table internal id.
I found an alternative route to achieve what I tried to achieve, so getting the error is no longer needed. I generated a uniquer tableid and compared that with the nested table internal id.
Hi , thank you for reaching out to the Microsoft Fabric Community Forum.
May i know if 'I found an alternative route to achieve what I tried to achieve, so getting the error is no longer needed.' mean your issue is solved. If it is, please share the insights here, which will help others with similar queries.
Also, please consider marking the answer 'Accept as Solution' so others with similar queries may find it more easily.
Thank you.
I am trying to capture the current query in the #sections table in Power Query
for what purpose? You already know which query you are in?
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 5 |