Has anyone ever used an absurdly long class list? ...
# administration
k
Has anyone ever used an absurdly long class list? Talking thousands and thousands of records. Original design was custom records - but we don't have support for those on a couple key integrations.
s
are they crazy. Why not categorize them into parent child relationship - at least will be easier to handle
j
I remember having performance issues with a client that had thousands of locations way back when, but I think there's a lot more hooked into locations than class/departments.
k
Trying to do an integration with some banks/credit cards - and they don't have the ability to add custom fields. They have the class field. We're doing Expense approval codes, like "CLIENTNAME1235Trip3.11" - then we're doing some reports on budget vs actual using the codes.
s
why not use GL impacting custom segment?
k
because the integrations don't allow it
My option not using class is to create a script and have them record text.
Which is not great.
s
wow
k
cause someone will type "ClientName12354Trip3.11" instead of the first name haha
It's an expense management process - where their customers have a "budget" for certain actions like trips or company parties, etc and so then the expenses need to be recorded against that budget
so they will charge them on credit cards/bills/etc.
I just hate to waste such a good field as the class field on this though
s
nightmarish situation - no way to stop them from messing up unless have naming convention check some how
k
Well, was going to script the lookup and do error handling, but yeah. Not a huge fan.
I think I am just going to bite the bullet and use Class in sandbox and see how they like it.
I did find out there's no limit on the number of records except for performance. And I'll have them inactivate the records over time.