Scorecard 2.0 Mass Edit Report only pulls in first 100 lines
CS Reports & Dashboards
We are currently working to build reports on Scorecard 2.0 for the long tail of our customers (25,000+). The hope was to do this using the "mass edit" report type which would allow for our 1:Many CSM's to filter various columns in the reports to identify trends. However, it appears that only the first 100 rows are being pulled into the report and being applied when filtering.
Is this a bug? Or is this a limitation that will be addressed in the near future?
Is this a bug? Or is this a limitation that will be addressed in the near future?
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
This looks like a bug and not intended behaviour. Could you please raise a support ticket for the same? We would have to dig deep to understand better.
Thanks
Abhishek S
This post is now more of a enhancement request vs issue.
To Add, I will also say we it probably a good idea for the application to have this, seems unrealistic to short each page, when you want to see all read accounts.
We
want to sort primarily by $ACV, but when we do, it only sorts the ACV of the
first 100 records according to the alphabet, so we see the ACV sort for
customers A-B which is not an accurate sort by ACV of the desired customer segment if
there are more than 100 records.
It caused us confusion when building and using the Scorecard Mass Edit table, and runs counter to the way every other Report / Dashboard functions in Gainsight, where we experience the desired behavior of ALL records being sorted rather than just the first 100 in view.
The purpose of a sort is to find the customers that are highest or lowest on some particular metric of interest. Limiting that "scope of sort" to the 100 records that happen to be in view is misleading, at best, and results in bad business decisions, at worst.
Since the above discussion is referring to sort functionality this is not a bug.Below is the exact behavior of
Scorecard 2.0 Mass Edit Report.
Sorting: Technically this is called Client-side sorting. Yes, this works on first 100 lines only.
Searching/Filtering: Technically this is called Server-side searching.This will search on whole data set.
We have this in our road-map to make sorting & searching work on the whole data set.ETA is not available currently .
We just invested a lot of effort into recalculating our scorecard measures and weights and converting to scorecard 2.0 so to encounter this now is really disappointing.
Our engineering team is working on both of these and the goal is to have the search (aka filtering) completed before the Winter release and updated via a patch release. Sorting is a bit more technically challenging and is being targeted for our Winter release (if possible sooner, we will try to do that).
"Search" in the Mass Edit Report will now work on the entire dataset (there were some issues with this, which have been fixed with the latest patch).
I believe Sort still has a limitation though, and is restricted to the 100 records 'in view'
But...when working with client server data sets, it's going to be better to filter first and then sort (so you're only pulling the data that is relevant).
So in the use case for this report (and with respect to the current limitation on sort), it is recommended to filter the data set as much as you can first.
We need to be able to see reds and yellows holistically across the entire customer base, not 100 customers at a time. This breaks several of our dashboards that we use in our at-risk meetings and I will have to try and figure out some kind of work around until the winter release. If there's anything product can do to prioritize this we'd appreciate it. We're at a critical point in our organization's adoption of Gainsight, and this is going to be a tough one to explain to managers and executives. Moving to scorecards 2.0 should come with a huge disclaimer that you'll no longer be able to utilize UI views and thus, not be able to sort your dashboards by scorecard color.
Thank you for your consideration.