Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi All,
I had been experimenting with using an OData connection to "https://graph.microsoft.com/beta/users" the last few weeks as a good way to pull in live organizational user data. This had been working like a charm for a few weeks. But the last few days, any time I tried to refresh the data I would get the following error:
Expression.Error: The field 'displayName' already exists in the record.
Details:
Name=displayName
Value=
I thought maybe I had renamed a column something I shouldn't have but I couldn't find anything. I finally just tried to create a new connection in a different report and it wouldn't even load the data and would return the same error. I'm at a bit of a loss. Anyone ever see this before?
Thanks!
Hi @gghneim,
Please check the "Applied steps" in query editor to find which step caused this error.
When you tried to create a new connection, please clear the cache (File->Options and settings->Options->Data Load) and test again.
Regards,
Yuliana Gu
I'm getting an error similar to this. The full error is:
An error occurred in teh 'Fetch' query. Expression.Error: The field 'Priority' already exists in teh record.
Details:
Name=Priority
Value=
I don't recall creating a duplicate field titled priority. Also, the shown applied steps don't seem to have the same field name either. I'm not sure if there is an applied step that is missing or something else that I am missing to solve the error.
I was having the same issue and this is how I solved it.
Go into your query editor and click on the query showing the error/warning icon (triangle) - usually the panel on the left of the data tables. You have to look at your applied steps (panel on the right) and find at which point your data still looked like you wanted (click on each step. Essentially, the step immediately after is responsible for throwing the error.
Thank you for the reply @v-yulgu-msft.
I removed all the applied steps before. It is occuring on the initial load. I cleared the cache as you advised but still no luck. I'm starting to wonder if the Microsoft Graph feed is the problem.
I'm having exactly the same issue - any resolution to this yet? It does seem like there is an issue with Microsoft Graph
Same issue here, worked fine a few weeks ago, now initially had to use an embed token to get access and when I do that I get the same error, must be something with the graph api that's changed.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
113 | |
97 | |
85 | |
70 | |
61 |
User | Count |
---|---|
151 | |
121 | |
104 | |
87 | |
67 |