Re: D2W: Pattern for complex object creation
Re: D2W: Pattern for complex object creation
- Subject: Re: D2W: Pattern for complex object creation
- From: Paul Hoadley <email@hidden>
- Date: Fri, 30 Mar 2012 11:26:27 +1030
On 30/03/2012, at 10:30 AM, 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.
Working as intended—thanks Ramsey.
I'm currently using ERD2WEditToOneRelationship (as a popup for the Practice), and ERD2WEditToManyRelationship (as a browser for the Billables). Are there ERModern variants that will also work with restrictedChoiceKey like this?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden