Portal Validation problem

[liltbrockie]

Hello .. having a bit of a problem here...

I have a portal that represents products for an order.

There is a validation on the field "Colour" such that it will not allow the user to have more than 1 colour (done by Count Values)

Now the validation works... but upon pressing ok after the validation warning, I am dumped back to the first portal row and NOT the portal row in question... (the last one)

Any ideas?

[liltbrockie]

After a bit of experimenting I can say that the validator will return you back to the correct portal row only when any of the validation rules except "by calculation" are used.

So it all works fine except when using validate by calculation. When using validate by calculation I am dumped back to the first portal row.

[liltbrockie]

Me again! :-)

I have attached a very simple example highlighting the problem

Try and enter a price of anything other that 5 in to the price field for the last portal row.

The validation will fail... and when you press no, instead of returning you to the correct portal row you are taken to the first!

Is this a bug?

portal.zip

[db_ugh]

I am having a very similar problem but with a different validation constraint. I have my portal rows reverse-sorted by Date, the first column, FWIW. New rows are naturally entered at the bottom. The rightmost column is 'Always Validate', 'No override', and 'Not Empty'. If you try to leave the rightmost column of a new OR existing record empty, then click outside the portal to force a commit, you are dumped to the incorrect TOP (most-recent-by-date) row, albeit in the correct column.

Can anyone elucidate?

Edited June 1, 2010 by Guest

[PHS]

I am struggling with the same issue. To make it even a bit tougher on my users, the field uses a value list and the validation is against the same Value List. So, the user is making a mistake on say the 3rd row of the portal, sent back to the first row, the value list drops down, and they are unable to click on the 3rd row to fix their mistake.

Did you find a solution to this issue? Any help is much appreciated.

[Vaughan]

If users can only select a colour once, create a text field in the related table with an auto-enter that concatenates the primary key and the colour value (with a separator such as a vertical bar). Validate this field to be unique.

If adding the field to an existing solution, remember to set the values for this field for records that have already been entered, otherwise the validation will appear to not work.