Error connecting to Adobe Analytics Power BI Connector 2.0 | Community
Skip to main content
Level 2
August 23, 2023
Solved

Error connecting to Adobe Analytics Power BI Connector 2.0

  • August 23, 2023
  • 9 replies
  • 8020 views

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. 

 

Thanks in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Vernon_H

Just got the root cause from Adobe Support:

"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."

 

All seems to be working again.

9 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 23, 2023

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...

Vernon_HAuthor
Level 2
August 23, 2023

Thank you Jennifer, the 1.0 connector works perfectly fine with the same references. Seems to be an issue with the 2.0 connector alone. 

I have raised an Adobe support ticket and hopefully I'll get a response soon. 

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 24, 2023

Good luck! Hopefully you can get that resolved soon.

Level 2
August 23, 2023

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?

Level 2
August 24, 2023

Did it get fixed? we have been experiencing the same problem for the last 2 days. 

Vernon_HAuthor
Level 2
August 24, 2023

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. 

Level 2
August 24, 2023

@vernon_h Please keep us updated on the fix.  Thank you!

August 24, 2023

Experiencing the exact same problem when refresh failed overnight. 

Level 2
August 24, 2023

Do we know whether this is a problem for Microsoft or Adobe to fix?  

August 24, 2023

I'm experiencing the same issue since yesterday too when a few of my reports were refreshing. 

 

I have opened a case with adobe so hoping they can help with this

August 25, 2023

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!

FarazHusain
Adobe Employee
Adobe Employee
August 28, 2023

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. 

August 28, 2023

Hey Fhusain, thanks for that - are you in contact with Microsoft to clarify this? 

FarazHusain
Adobe Employee
Adobe Employee
August 28, 2023

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.

August 30, 2023

FYI: for me it worked fine again as of today! Not sure if it works for y'all as well?

Level 2
August 31, 2023

It is working for me as well today.  If anyone knows the reason for the issue, can you share?  I see a few possible reasons discussed.  Thank you!

Vernon_HAuthorAccepted solution
Level 2
September 1, 2023

Just got the root cause from Adobe Support:

"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."

 

All seems to be working again.