Summary
portal filtering and sorting don't work if allow creation of related records is turned on
Product
FileMaker Pro
Version
12v3
Operating system version
MAC WIN
Description of the issue
create a portal
use a relationship with allow creation of related records on
turn on filtering - use a dummy predicate always true
filtering and sorting doesn't work if new records are added to portal
- sorting works if records are open until newly records appear
Steps to reproduce the problem
create a portal
use a relationship with allow creation of related records on
turn on filtering - use a dummy predicate always true
filtering and sorting doesn't work if new records are added to portal
- sorting works if records are open until newly records appear
Expected result
sorting and filtering works as expected independent of record open state of all records within portal
Actual result
sorting stops working as soon as records in portal show up with record open state 1
filter turned on breaks all calcs in custom function scanning over all portal rows using recursive custom function with getnthrecord ..
Exact text of any error message(s) that appear
no error - just no filtering or sorting takes place
Configuration information
no plug ins - file standalone - or on server -same issue
Workaround
no workaround possible - because portal with allow creation of related records is the only way to implement transactional behavior.
PLEASE FIX!
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:
True
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.