Using Windows XP, I cannot reproduce this in FileMaker 12.0v3
In my Known Bugs List Database, I have a portal on the bug report layout that lists Categories. It's set to sort by category in ascending order and allow creation is also set. It works just fine. I can select a value in the "add" row of the portal and when I click the layout background to commit the record the portal updates to show the category records in correct ascending order.
I then went into layout mode and entered an "always true" portal filter expression:
The portal behavior did not change.
It then tried this always true filter expression:
Not IsEmpty ( Categories::BugID )
and again the portal remained fully functional.
I'm using a classic themed layout so if you are not, that may be a difference here.
sorry i wasn't more specific - here is the discussion where i tried to outline it further.
thanx for looking into this.
(i might provide a demo file soon)
Well having read the technet discussion it's still not clear to me what you want to have happen differently. Thoughout that post, you describe the process as "broken" but do not go into detail as to how, exactly, it was "broken" for you. This lack of detail will handicap any efforts by FileMaker techs to reproduce the issue you are reporting.
it is the first phrase where i explain:. "setting the relationship to allow creation of related records breaks portal-filtering and portal-sorting as soon as you enter a new line."
so what is so difficult to understand here? by breaking i do imply - sorting stops and filtering stops.
Since this does not happen on my system when I try to replicate the issue. filtering and sorting still works. Thus, I am trying to identify exactly what is different between what you and I are doing.
do you have mixed records in your portal - mixed regarding recordOpenState (0, 1, 2)
do you ccontrol committing via an OnCommmitTrigger ?
i will provide shortly a demo file - thanx god someone savvy from GB could confirm it on the mentioned discussion ..
i experience a lot of weird behavior within portals as soon as the record open count > 0 ..