Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

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

Fox_mulder007
Level 2
Level 2

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
Khurshid_Alam
Correct answer by
Employee
Employee

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

View solution in original post

7 Replies
iamjasona
Level 3
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.
Fox_mulder007
Level 2
Level 2
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.
iamjasona
Level 3
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.
Khurshid_Alam
Correct answer by
Employee
Employee

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

View solution in original post

stefans13438214
Level 1
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

a_echols
Level 1
Level 1
We're having the same issue and submitted a Customer Care ticket.
jantzen_belliston-Adobe
Community Manager
Community Manager
Was Client Care able to solve this issue?