The good thing is that it only needs to be run once and it doesn't need to be a dynamic query - so we can let it go and then receive the results. So it can be a bit inefficient if we need it to be.
Thanks, that's pretty much the direction I figured I needed to go - adding logic within the loop so it knows what it just picked and what should happen after that.
Pick first session, if lecture we need a break, if workshop we need 2 more workshops then a break, etc.
It sounds like they're complicating the issue now though, and they want attendees to have "preferences" and then we put them in their preferences first. Ugh.
The good thing is that it only needs to be run once and it doesn't need to be a dynamic query - so we can let it go and then receive the results. So it can be a bit inefficient if we need it to be.
Thanks, that's pretty much the direction I figured I needed to go - adding logic within the loop so it knows what it just picked and what should happen after that.
Pick first session, if lecture we need a break, if workshop we need 2 more workshops then a break, etc.
It sounds like they're complicating the issue now though, and they want attendees to have "preferences" and then we put them in their preferences first. Ugh.