Expand my Community achievements bar.

Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!
SOLVED

Calculated metrics - "This metric is not enabled for this report suite"

Avatar

Employee

Hello, 

 

Since this morning, I'm seeing the following error message when dragging drop some calculated metrics (all the calculated metrics are not impacted). 

 

Does anyone know why ? They were always working from the day they were created.

 

Thank you

 

Fox_mulder007_0-1610038800040.png

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Please report this to Customer Care so that we can look into this error.

View solution in original post

7 Replies

Avatar

Level 3
I'm noticing this, as well, with some of the standard Adobe calculated metrics. Have an existing Workspace project that had Revenue / Visits in it, but now getting an error on that metric that says "This metric is not enabled for this report suite". So, I create my own metric....and then attempt to do a Compare Time Periods on it. However, the Percent Change column now has the same message. Nice.

Avatar

Employee
Hi @iamsasona, Thanks for the feedback. For instance if I choose "New visits" (which is one of our calculated metric), it is working on report A but not on report B which is really odd.

Avatar

Level 3
Yep, I'm getting similar behavior there, as well! In some panels, the new Adobe Revenue / Visits calculated metric is functioning properly. Ditto with the Percent Change. Very odd, indeed.

Avatar

Correct answer by
Employee Advisor

Please report this to Customer Care so that we can look into this error.

Avatar

Level 1

I'm having exactly the same issue. I hope Adobe will give priority in fixing this. I don't think it's very helpful to ask us to create a support ticket, since it seems to be a general bug that needs to be fixed on the Adobe side

Avatar

Level 1
We're having the same issue and submitted a Customer Care ticket.

Avatar

Level 10
Was Client Care able to solve this issue?