There have been some issues reported with portal filtering on a FMP12.2 client running from FMS12.1
THe issue i have been having is the not equals function is ignored.
I am seeing problems with the = as well works fine till you change the value of the global referenced in the filter - sometime updates sometimes it doesn't...
what is latest version of the server software?
Currently the latest of server is 12.1
Shouldnt be too much longer for v12.2
I had also had an issue whereby the refresh window script step doesn't seem to work in a script, requiring me to manually select the "Refresh Window" command from the "Records" menu at the top of the screen. For some portals I have changed the nature of the relationship to force the refresh (e.g. including a setfield step for one of the fields in the relationship), but I would rather not complicate the relationship if I could allow the portal to refresh using the "Refresh Window" step.
The refresh issue is a common problem in earlier versions of FM, and not just an FM12 issue. Especially if the portal is related to a table in a different file.
First step: Put a script trigger on your global field. When it is modified, try a simple commit script step.
If that doesn't solve it, experiment with some additional script steps. According to the Under the Hood session at Devcon, the Refresh Window script step will force a refresh immediately, with less screen flashing on PCs than in the past. I haven't tested this yet!
Have your trigger script first commit, then add a refresh window. That should work. If not - maybe some more details on what is being entered in the global field, what the relationship consists of, etc. I have also solved this problem use a pause/resume script step set to 0 seconds, freeze window then enter browse mode, etc. etc. to force the refresh.
As long as the relationship is valid, something along those lines will refresh the portal.
Maybe off topic but...
I found a little bug after upgrading to 12v2.
In my cases, when i have a field that could assume value empty or equals to 1 and portal has filter like table::field ≠ 1, portal doesn't work properly!
I have to change in every situation the calculation with Empty ( table::field )
Not simple, in a big scenario.
1 of 1 people found this helpful
- I added a commit step - didn't help I left the step
- added a refresh - didn't help - I left the refresh
- went back to refresh - checked option to flush cached join results
Now working fine
Yay! Sorry to hear that FM12 hasn't solved this problem, but at least we still know what to do to fix it..