Virtual Customer Advisory - End User Reporting

I have conflicting feelings about this feature - on the one hand it could empower CMS/COMs/Managers to get the information they need to make decisions quicker. On the other hand, the reporting structure is very complex and I am already having nightmares of SFDC style custom reports where there is no source of truth for any given metric as everyone has 20 reports on the same thing with slight variations.

This is exactly the concern I have as well.  Between the complexity of our environment, and the complexity of the reporting structure, I’m not confident that allowing users to build their own reports would yield consistent/accurate results.  My hope is that the feature would be able to be toggled on/off, based on where it is appropriate for the customer’s user base.

@Melissa_Young A feature toggle is super important, you’re right. I made a similar comment here 

about allowing user-editable field displays. I don’t think it should just be on-off, I think it should be permission group based so you can enable it for some users and not others. Otherwise, if your exec insists on using it you can enable a free for all, or you’d have to make them an admin which maybe you don’t want either.

Good discussion in here so far. FYI @rakesh 

Count me in. 

I also subscribed. As an admin, I'm getting quite some questions to create custom reports on this or that. I'd like to open up the report builder for more people, but the underlying data model with GS standard fields (same names on every object) and many lookups is very confusing for people who are not used to work with it on a regular basis. Our Customer Marketeer is already struggling when she has to set up the target groups for email campaigns in Journey Orchestrator.

Hi! Just registered for it. I am using it from some months and on one side I really like it, especially when integrated with Data Designer, on the other side I believe it could/should be made more customizable.

This has been requested by our users but I also share the same concerns as above. I think exposing certain fields/filters or defining which objects/fields are exposed to end users might help. Signed up!

Would love to brainstorm more around this! 

Yes, please make a set of optional permission settings that can be turned on and off for users. It needs to be more granular than what it is today (in NXT) to choose not just whether or not a person can create reports, but can they edit them, delete them, etc.