@brianwclayton1969
Okay, we're talking about casework families with the proposed 10 parameters on your attached file.
Depending on the order involved, the number of remaining parameters to sort by will diminish due to the realities of the unitized nature of casework modules. I think you need to confirm the required sorting order in able for you to guide your client in the direction of a workflow that will enable them to produce the table in a usable form.
If I assume that the schedule titles are already in the correct order (ex. A = first sort, B = second sort, etc), I would off the start suggest that you have distinct schedules filtering for each building and floor. If totals are required for the whole project, create a summary table that shows totals for what they wish to count.
2 down, 8 to go.
Keying? If it is a yes/non column in the sense of does the casework include access security in the form of a key or is it a reference to the key path number for door hardware. Assuming a yes/no, it seems to be a strange thing to sort by rather than filtering and created additional distinct schedules.
Self price? Strange to want to sort by the price before knowing the part number?
Unit number. Yes, an important parameter to sort by when having to find a specific casework item and usally tags on some plan somewhere.
ZZ Detail? Is this a detail drawing reference to a sheet? Strange to sort by sheet before Room number unless you have a huge amount of details on a sheet!
ZZ part? If we assume that each casework family has a unique ZZ part number and shares a Unit no. with other ZZ parts, Is your client modelling them with embedded casework families such as a door handle family within a cabinet casework module? This will also limit the way to sort and tabulate totals.
Room number. Seems a bit deep in the sorting order to be useful. If the ZZ part number is for a door handle, in a single reference to a detail on a sheet that is in a casework unit on that detail for a specific price assuming a the same unit can have a different price in a different floor ... You see where I am going?
So if this information needs to stay in Revit, you need to work out a work flow that divides and filters then sorts to a usable depth of 4 parameters.
If not, exporting to a dedicated spreadsheet seems to me the other option. From there, bringing the sorted information back into Revit for documentation purposes is also possible.
-luc