For those of you who have worked with me in the past, I'm continuing to build on my social service case tracking system. I have a requirement that the Program (kind of like the OOTB Product) selected at the Case needs to be on a lookup on the Purchase Order to which I can create and filter another lookup so that the user can only select a sub-program which is filtered by Program.
Here are my relationships:
- Case (where Program is selected) has 1:N with Purchase Order.
- Purchase Order has 1:N with Purchase Order Line Item.
I need a filtered lookup on Purchase Order Line Item that is filtered based on the Program selected on Case.
I've added a Program lookup to both of the child entities. I populate the value with a workflow "On Create" to Purchase Order. My challenge is doing the same thing with Purchase Order Line Item. This is where the filtered lookup is and the user needs to select that before the record is saved, but the value for the parent lookup isn't set by that workflow by that time. I've made it an "on create," but there is a conflict in that the population of Program hasn't happened by the time the user has to select Sub-Program.
I hope this makes sense. It's kind of a chicken-and-egg issue and I'm struggling to understand when things REALLY happen in the technology stack from a real-time workflow.