I’m trying to figure out how to display Advance records grouped by Primary Originator, where the aggregate metric is sum of the “amount” field and count of the “ID” field.
I think my issue is that I only need the row grouping and not the column grouping, but it forces you to choose both.
A workaround is to group the “date funded” field by month, but for some reason no data shows up.
There are some filters applied, but I noticed this issue before any filters were applied, so I believe they are unrelated.
Do you know if I’m doing something wrong or if there’s a different way to accomplish what I’m looking for?
What do you have in the values field, is the ‘Amount’ field and aggregated by sum? Can you screenshot it?
Amount Field:
ID Field:
Filters:
(But when I apply those same filters + applicable permissions in the Data tab, 18 records appear.)
So it doesn’t work when you apply filters in edit mode but does when you apply them front end? Is that correct?
If so, does removing the “Logged In User” from you editor filter so its sort of like the below work?
Hard to tell how its setup but currently that’s set to only show records from, I’m guessing you (logged in). If the permissions are being applied at table level do you need to apply them again in the filter?
if not, Ill leave it to the experts to help 
I meant from the backend Data tab, not the frontend app.
Sadly, removing the user filter did not have any effect.
It’s a Reports page, so e.g. even if a Manager has access to all his users’ data, he may want to filter by just 1 or 2 users to check on their performance.
Thanks for your help.
If you remove those 3 filters from editor and apply no filters front end, how many records show?
Still none:
That’s why I think the issue is with the charts, not the filters.
I’m running 20+ pivots with no problems so I thought it may be the filters applied
I’m curious how the logged in current user filter is working with the front end filter or against it.
You’ve probably already done this but just in case.
-
Id go all the way back to the start and just have it as a table (not pivot) with no backend or frontend filters to see if the records show?
-
If they do, then add the backend filters as above, do they still show?
-
If they do, does it then revert to zero records when changing to pivot.
Hopefully you get it sorted, frustrating when it isn’t. 
Thanks for the suggestions. I can’t remove the backend permissions because this is a production environment. I did remove all the frontend filters, though, and the Table displays more than 0 records. But it shows that all records have “No Value” for the Primary Originator field:
However, in the backend Data tab I see clearly that all Deal records have a Primary Originator value.
You can see I put the Workspace filter, because the one backend permission for this user (who has the role of Super Admin) is for Workspace:
So even with the backend permission applied, there seems to be a bug where it recognizes no value for Primary Originator.
Perhaps the Pivot Table shows is set not to show a grouping for “No Value”, so it shows 0 records instead?
So at which step below is it breaking?
- Creating the basic table?
- Adding editor filters?
- Adding front end filters?
- Converting to Pivot?
It appears the basic table displays correctly in your screenshot, its just grouped by Primary Originator, if you set the pagination to 116 does it then show all originators (grouped with count)
I can’t remove the backend permissions because this is a production environment
Sorry, I meant editor filters, not table permissions. So basically you have a basic table frontend with no editor or frontend filters (dates in your example).
If you have a raw basic table front end that displays zero records then I’d guess its table permissions. If it displays some data then its not permissions, probably filters or even grouping.
Carlos from Support was able to figure it out!
Could you try setting up the row grouping again and choose a different subfield like name or email for Primary Originator instead of the default value?
I think Primary Originator > Primary Originator doesn’t work as expected because it’s just a display reference from the lookup. Subfields like name, email, or ID should work for grouping.
I just chose Primary Originator > Full Name instead of Primary Originator > Primary Originator, and it works now.
Thank you @garyGHL for your help debugging and thanks to the Support team for the fix.
2 Likes
