You need to sign in to do that
Don't have an account?
Richie Landingham
Data Structure for Lookup Table
Hello Everyone,
Right now I am working on an IRS Standards calculator for our internal users, what this does is takes the clients zip code, and from there using the Google Geocode API will be getting the correct county.
The problem I am running into is about how to structure the table to look up the standards. Esentially what I will have to look up is every County in the United States (So about 3222 Counties), Each county has a standard for how many household members, up to 5. So there would be 7 Columns.
State:
County:
Standards for 1 member:
Standards for 2 member:
Standards for 3 member
Standards for 4 member
Standards for 5 member
But, is this too many records to be using for a custom metadata type? What would be best practice for this? I tried to find an API I can reference for the standards, but unfortunatley I couldn't find anything.
Right now I am working on an IRS Standards calculator for our internal users, what this does is takes the clients zip code, and from there using the Google Geocode API will be getting the correct county.
The problem I am running into is about how to structure the table to look up the standards. Esentially what I will have to look up is every County in the United States (So about 3222 Counties), Each county has a standard for how many household members, up to 5. So there would be 7 Columns.
State:
County:
Standards for 1 member:
Standards for 2 member:
Standards for 3 member
Standards for 4 member
Standards for 5 member
But, is this too many records to be using for a custom metadata type? What would be best practice for this? I tried to find an API I can reference for the standards, but unfortunatley I couldn't find anything.