The Adobe Analytics Power BI connector 2.0 was working perfectly fine but just this morning it started to return the error "The field 'name' of the record wasn't found.".
Has anyone encountered the same issue or know what could be the cause?
We have tried clearing and re authorising the permission but the issue still persists.
"The report suites collections API is being replaced by a newer data suites API. The initial rollout exposed the missing fields behind an expansion. The service was rolled back to the original report suites API to resolve the issue."
I don't use Power BI, but it almost sounds like someone may have renamed something in your backend? Or maybe there is a temporary server issue that may self resolve...
Given it used to work, I think it might be worth checking to see if anyone made any changes (any dimension or event name changes, or possibly changes to segments or calculated metrics?) I would start by checking specifically the elements that are being used by your connection...
I am experiencing the same issue for the first time today with Adobe Analytics Connector 2.0. It has always been fine before. Has Adobe and/or Microsoft changed something?
With the issue, I cannot go past the company name to see dimensions, metrics for selection.
Can anyone from Adode help with this issue? Or is this a Microsoft issue to fix?
Nope, I got on a call with Adobe Support and they seem to have the same issue on their end (using another account). Connector 1.0 works though (but obviously not going to be easy converting queries over) - I'll just be waiting till they fix it... But if there's an update I'll update this thread.
I've also been experiencing this error with Adobe Analytics 2.0 connector since Monday or Tuesday of this week, preventing my Power BI reports from refreshing. Its at least positive news that support was able to replicate the issue. Thanks for the post and updates Vernon_H!
Hey All, In one of the cases I have looked at the traces produced by Power BI. It can be enabled under Option > Debugging > Enable Traces.
As of now, it seems to be an issue from the Power BI end, since Analytics APIs are returning status code 200, and the error appears to be generated from the Microsoft Mashup engine.
A client has logged a ticket to the team; the Microsoft team is looking into it from their end as well. I would suggest logging a ticket from your end too with the Mashup traces.
Yeah, it is odd. But at this moment, we don't see any Analytics API failing, so if you have a ticket logged to client care, maybe you can share the logs and they can review this and see in your case what exactly happeing.
In my case, it wasn't working with both the connectors and it was happening with some users, for other users it was working as expected.
Something definitely odd. So need to be checked from both ends.
