new record not appearing?

[mark.christiansen]

I've got a portal that points to related rows via a simple foreign key in the child table. When I type in one of the portal's fields, the row "disappears" after I leave the field. I know the row I was typing in is supposed to stay there and add a new empty/insertion row at the end of the portal. But this is not occurring.

If revisit the parent record, then I can see the proper number of rows in the portal -- so the new record was properly created in the database. But this requires me to flip to a different parent row and then back again.

Could this somehow be related to new layouts for the child table? When a portal creates a new row, does it somehow use one of my layouts to do this? For instance, sometimes I get an error that a particular field in the child table requires a value, but that I'm not using a layout that supports data entry for that field.

Thanks for any debugging tips!

[Ocean West]

what is your primary key and foreign key? are the field types the same?

[mark.christiansen]

They are both Number (with the primary key being a serial number too).

[Søren Dyhr]

I would say it's quite a challenge to make this happen, unless you have some kind of "auto-enter calculation replaces existing value" on the foreignkey as well???

--sd

[mark.christiansen]

Hm -- no updates are taking place to the keys involved. Could there be some error that isn't getting reported properly? When I do my little previous record-next record trick to get the portal refreshed, I get an error message for the child table:

"FieldX is defined to require a value, but it is not available on this layout. Use another layout to assign a value to this field."

Is it somehow related to the portal insertion? But the field in question is setup to have a "0" as its default data item.

[Søren Dyhr]

I can't get it, couldn't you upload a template showing it??

--sd