On Mar 29, 2012, at 4:57 PM, Paul Hoadley wrote: Hi guys,
David, I'll look at your solution shortly, but Ramsey's here was closer to what I was envisaging. On 30/03/2012, at 9:57 AM, David Holt wrote: On 2012-03-29, at 4:23 PM, Ramsey Gurley wrote: More than one way to skin a cat here. I'd probably just set up a wizard.
step 1, choose a practice with an ERD2WEditToOneRelationship that filters the list to only practices with billables that have no invoice.
I would move Step 3 into Step 1, only because I want the date to be part of the filter on Billables. (I might be running a couple of days behind on the Invoice, and already have new Billables for the current month. It really needs another "cutoff date" attribute, probably doesn't even need to be persisted, as opposed to the "date on the invoice". But that's a detail I can work out.)
Yeah, if date makes sense first, then that's better. You can then filter your practice list by date, then your billables list by practice and date. Both toOne and toMany components look for a restrictedChoiceKey.
step 2, choose billables form a filtered list for that practice with an ERD2WEditToManyRelationship component.
Oh, OK, I was thinking about it incorrectly for some reason, figuring I had to populate the Billables relationship from within Invoice itself after date and practice had been set.
Can you use information entered in Step one to inform step two?
Presumably I've set Invoice.date and Invoice.practice in Step 1, and I can use those values in Step 2? I'll try it and report back.
|