I'm struggling to figure out a solution for this, so I figured that I would ask here. What we are looking to do is have all of our items categorized for the purpose of organizing how our website will display all of the filtering options for certain top-level categories of products. The following is an example of how we would like to do this on our site. Each "value" entry can have multiple items "linked" or "associated" to it: • Hand tools (this is the top-level category) ◦ Drive Size ▪︎ Value 1 ▪︎ Value 2 ◦ Type ▪︎ Value 1 ▪︎ Value 2 ◦ Measurement units ▪︎ Value 1 ▪︎ Value 2 I'm not sure how we can effectively do this directly on the Item record, so I figure that the optimal solution would be some sort of custom Record Type or something like that. Has anyone else had to do anything similar to this? If so, how did you do it?

Create a parent child relation custom record. Like we have for department,location, subsidiary, etc Parent category, Then each child category, the child category record will have the parent tagged Source that record in a custom field in item record, select the category.

Thank you @raghav. Will try this out and let you know if this works!

What you are describing is essentially product attributes underneath a single level product hierarchy (Category). Category could either be it's own customfield, or you use the native class field to break out category. From there, I would simply add custom fields to the item record for each attribute with each referencing a list. These list records would be unique to each field with all the possible values. In your case, 4 fields - Product Category (if not using class), Drive Size, Type, Measurement Units. The website design should easily be able to stack them in a hierarchy like a pivot table would.

@Thor Hansen would I need to make custom lists for all of the different levels of the hierarchy?

It's recommended, yes. This way users can't add hierarchy values. For example, if Drive Size had options for 1/2", 3/4", and 1" and you did not use a List and allowed the field to be free-form text any user creating an item could enter "Screwdriver" for drive size and ruin the reporting.

@Thor Hansen thanks so much for your guidance!