Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!

Better ability to sync SAINT classifications across multiple rsids

Avatar

Level 9

7/31/13

Basically, I cannot select multiple rsids and edit SAINT classifications for xyz variable unless the classifications for xyz variable are the same for all the selected rsids.  This makes it really hard to change classifications across rsids, especially since there's no easy way to tell which rsids don't line up.  

 

So far I have found that the easiest way to figure this out is to use the Report Suites API to get a list of classifications for all rsids so I can see them all one screen and single out the offender(s).  IMO this is a step I shouldn't have to take!

 

I think a really easy to fix this is to add a "Use xyz rsid as a template" option, exactly how it's done for custom menus.  

2 Comments

Avatar

Level 5

7/31/13

This is a great idea.  I would love to apply a classification to any variable on any report suite.  Ideally there would be a configuration for the SAINT classification (via FTP) to either:

1. Skip the classifications that do not exist

2. Create the classifications automatically if they do not exist

 

It would make it flexible and easy to use without having to go and create a classification on a completely separate screen.  For that matter, it would be nice to manage and create classifications from the SAINT screen instead of (or in addition to) the admin console.

Avatar

Level 9

7/31/13

adamhaining: what worse is that the Admin/ReportSuite API is supposed to allow you to create/edit classifications for variables, but it is bugged.  Basically it works for editing exisiting columns, but not removing or adding.  So I couldn't even use the API as a full workaround for bulk rsid maintenance of SAINT classifications; all I can use it for is getting a list of the classifications and then manually change the offenders through the web interface (I have submitted the API bug to ClientCare and also posted on developers.omniture.com but I have had no luck in seeing it get fixed or even getting a response out of anybody)