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

Classifications | Flag which RSID are already enabled

Avatar

Avatar
Shape 1
Level 1
noemie_greyl
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
Applaud 5
View profile

Avatar
Shape 1
Level 1
noemie_greyl
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Shape 1
Applaud 5
View profile
noemie_greyl
Level 1

13-07-2020

Screenshot 2020-07-13 at 12.33.21.png

 

When doing classification for multiple report suites, there is an alert when one or more report suites have a different/existing configuration:

The classifications for this report do not match for all report suites. Only classifications that match exactly can be viewed and edited across report suites.

 

If it is smart enough to know that one or more report suites have a different classification, could it please indicate which report suite(s) are affected? Spending a lot of time on unraveling this mystery..

1 Comment

Avatar

Avatar
Validate 1
MVP
AlexisCazes
MVP

Likes

185 likes

Total Posts

420 posts

Correct Reply

198 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile

Avatar
Validate 1
MVP
AlexisCazes
MVP

Likes

185 likes

Total Posts

420 posts

Correct Reply

198 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile
AlexisCazes
MVP

14-07-2020

The best way would be to contact customer care to be honest.

 

You might think that the error would flag only if classification tree is different but in some cases even if you have same classification tree, in reality in the backend the mapping is different.

 

rsid1

 

report1 == id1

report2 == id2

report3 == id3

 

rsid2

 

report1 == id1

report2 == id2

report3 == id4

 

So while you would think that the classification config is the same on the client-side, in the backend it is actually different. That happens when you would have had another classified report but you removed it after adding report3