Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Since 06/30/2020 my dataflows that connect to SharePoint data have failed and keep failing.
It apears the source (Name = have changed from Names to GUUID's.
Has anyone seen this?
If i connect to a new instance of the list as if I am trying to create a new dataflow, the Navigation parses a GUUID.
Than I can see the data fine.
Solved! Go to Solution.
Hi @ScottBrown ,
If you wan to change the datasource, you should ensure original steps can works on new source.(the steps which start from "Navigation")
For example:
Your original table name is "ImportTracker", but the new source not contain the "ImportTracker", it will show the error message which you mentioned.
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Correct Llang,
However, the list name has not chaned.
If I create a new connection to the Same "Import Tracker" list, it shows up as a GUUID instead per the atatched pictures.
Nothing changed on my side during this period, but something changed on the back end - not from me.
Now, the refresh no longer works.
The same issue exists on all dataflow entities that connect to SharePoint lists.
All other data sources ie SQl, file, ACCess and such that we use still refresh.
I tried the API suggestion, no luck. The issue is the Name scope changed on the backend by MS. It only appears to recognize GUUID, not the SP list name.