Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
5
Newest
 Supporter
Impact
~339 people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Sep
25
comment Intuitive way to present chained 1-N relationships
I like your idea of separate lists and see why you would need two places to store them if you are assigning workers way before activities are created. Rather than showing every worker for the Activities, I'd just limit the query to the workers assigned to the workOrder with a where clause.