Here’s a hypothetical that will explain my current project.
My client has ‘candies’… they can be of different ‘shapes’ and ‘flavors’. (ok, enuf with the 's)
I’d like to create a lookup table for each. Groups seems like the best option. So I’ll create a Group Shapes and a Group Flavors. Users can add shapes and flavors as they please.
Next up, I’d like them to get an updateable BAQ dashboard, that will run the Shapes vertically and the Flavors horizontally, with checkboxes as there vertices. If a user checks one, it would update to a UD0# table. Then as users add new shapes, they can go into the dashboard and select what flavors that shape is available in. Also, if a new flavor was added, then the current shapes could be chosen for that flavor.
From there, dropdowns would be populated with the flavors, based on what shape was selected.
I’m advanced in SQL, thinking I could probably do this with a pivot view on the two groups exposed as an external BAQ.
Am I crazy thinking this would work? Is there an easier way to accommodate this? In the Epicor world, this could be PartNum-UOM or something similar.