Toggle for Custom VRS Components auto inclusion/exclusion | Community
Skip to main content
New Participant
March 30, 2018
New

Toggle for Custom VRS Components auto inclusion/exclusion

  • March 30, 2018
  • 14 replies
  • 21163 views

There are two use cases for VRS component customization:

1: Specifying a smaller set of core components to be available in a VRS (auto-exclude anything new)
2: Removing specific components that might not be applicable to a VRS (but wanting everything else included)

By default, any new component created in the parent report suite is placed in the Exclude bucket, this works great for use case #1, but for use case is #2, we constantly have to be going into the VRS settings to move new components from "Exclude" to "Include".

It would be awesome if there were a toggle in the VRS settings to auto include, or auto exclude newly created components.

14 replies

Community Manager
October 5, 2022
No text available
jantzen_b
Employee
October 27, 2020
No text available
Andrew_Wathen_
New Participant
February 6, 2019

Hi Gigazelle, thanks for reaching out.

The ideas are definitely strongly related as the both relate to the way VRS curation currently affects the inclusion/exclusion of components.

However, my thread is very much focus on this impact on user created components (segments/calculated metrics).

Also, the suggested solutions are very different; the solution in this thread would not address some of the key issues I'd like to see solved such as the impact on segment sharing, segments being either available to all or available to none etc.

Which is a long way of saying I think they should be kept separate

Gigazelle
Employee
February 5, 2019

Hi Andrew, that's an awesome thread that goes into pretty solid detail on the issues you're experiencing!

Do you feel like these two topics are related closely enough for them to be considered duplicates so we can focus the conversation in this thread, or do you feel like the two topics are different enough to warrant their own idea?

Andrew_Wathen_
New Participant
February 5, 2019

Hi jen.lasser

I've got another related idea logged which goes into the details of the issues we've been experiencing:

Virtual Report Suite Curation: How did it get so messed up??

(somewhat regretting the slightly inflammatory title but guess it was a reflection of how frustrated I was )

Andrew_Wathen_
New Participant
February 5, 2019

Sorry to hear you are still struggling.  I sympathize greatly as we've had to abandon the use VRS curation until Adobe sorts this out  :-(

The confusion and impact on our end users was similar to what you appear to be experiencing.

I still come back the fact that I don't really understand why Adobe have included user created components (i.e. segments/calculated metrics) in VRS curation.

There are so many other better ways to manage access to segments/calculated metrics such as sharing, and workspace curation.

Jennifer_Kunz
New Participant
February 4, 2019

jen.lasser Alas, I have some followup- I'm doing a training on Wednesday and have given a training account the same sorts of access/rights that my users will have, so we see the same things. And now I see that without fuller rights to Virtual Report Suite admin, I don't even GET the "add new component" tick box-

This is what our users-in-training will all see when I have them create a new calculated metric. It's icky enough, I'm going to give up on using the VRS for now:(

Jennifer_Kunz
New Participant
February 4, 2019
Employee
January 21, 2019

Ok thank you guys for providing this added info! I will pass this along to my colleagues focused on VRS so they can take it into consideration for the next iteration of VRS curation.

Jennifer_Kunz
New Participant
January 18, 2019

Thanks for looking into this and responding, Jen!

That "component may not appear" message does help a bit, though the messaging is a bit weird (something more along the lines of "would you like to include this component in the VRS? Yes/No" would be much clearer, and if I'm in a VRS it should default to "included", since the assumption is I created the thing because I want to use it here) but I still feel like for bigger orgs particularly, it's going to be a mess to maintain.