RE: Re: 1 cset was pushed to core/stable: admin-validation-subform.xd: Change to ...

CC'ed to the KB list for better bookkeeping -- and further notes (if
necessary)

>> Site designers won't care how it works internally - they do need
>> to know how to define the property though :-)
>> 

And telling them how to do that was why I changed it.

Man that was a beast of a property to figure out.  Took me 6hrs to get that
far, because the first DD Object that I created didn't have an Item ID
field.

The second one had an Item ID field, but I didn't name it 'itemid'

What this resulted in, was multiple dd items for my object with the same
id's.  Which meant that the db calls bringing those items out from the db
were getting multiple records, when they really should have been getting one
record back.

I had assumed, that somewhere, deep down (perhaps with a primary key on the
DD Data table) there was something to prevent multiple DD Items with the
same id.

But at this point, I've got it working and talked a baraboom and anyone else
that was on IRC earlier today, how to setup and use subforms using the 'list
of children' version that I've got working.  I also posted to the KB mailing
list a quick How-To using the 'local' style.

I hope to have time this week to also post a quick how to for the other two
modes.

I'm still not quite sure what the point was of having a selectable link (in
the child style) w/o also having a selectable display title field.

The child style still needs a way to delete children, and to link in other
children that have been defined by the same object but by different
properties (or already exist in the DD Object from importation or other
sources.)

--
Mike C. {who likes a good challenge}