Validating Portal Records

[Scott Grumm]

I have a table "Payments" that is displayed in a portal and set to have records created via the relationship to the parent table. I need to validate all of the payments (records in the "Payments" table) made but they don't validate when the record is first created but they are validated when the record is updated. I am trying to figure out why this is happening and if there is a way around it. Is it possible the problem is because the validation refrences a related field?

It also looks like if a payment is deleted an unstored calculation using Sum() still counts it as well as a summary field. Is there any way around this?

Running FMP 8.5 Advanced on Windows XP

[bdam]

Giving this a bump since I have the same question/problem.

If you are validating a field which is shown in a portal it is not being checked/validated when you move on to the next record. So let's say you create 30 records in a row and one of them has an invalid field. Until the parent record is committed none of them get checked.

That wouldn't be _so_ bad if FM dealt with it a bit better. If something doesn't check out it doesn't go to the portal record that has the error, it always goes to the top record. Then you're pretty much screwed, you have to manually go through the records and figure out which one it is. If you revert the record you lose everything you entered.

I have a situation where they are entering a hundred plus lines at a time. We need to validate the field (an ISBN) but can't afford to lose our changes or manually check each one after the fact.

I've attached an example. The only valid entry is 1234; anything else is invalid. Create a mix of valid and invalid records in the portal and see what it does.

test.zip