|
Rey,
We have put this item on our bug list. The
filtered select should be pre-populating with the parent value.
One possible workaround is to remove the filtered
select entirely; if it is a foreign key field, then Plum will automatically pass
the parent's primary key value to the action page.
HTH,
Dave
----- Original Message -----
Sent: Monday, March 21, 2005 3:54
PM
Subject: [plum] Parent/Child form
problem
While I'm at it,
there's one other problem I'm having. I followed the requisite steps to
create a master/detail form set, using Organization as the parent and Services
as the child (tables properly PK/FKd, etc.). When I did this with the
example code from the tutorial, the Child form automatically populates the
Parent FKID in the appropriate id field, but that's not happening for
me. One potential problem is that there are a number of Org IDs, so I'm
getting a filtered select list for that field by default, but it's not
auto-populating the Org ID field. Is that expected behavior? Is
there any way to get the IDE to auto-pop the value, or do I have to tweak the
code? Again, any thoughts are greatly appreciated.
All the
best,
REM O-
|
