If the data's for the diagram are based on a relationship, maybe including the sort order in this relationship could be a workaround though that script-trigger would not be necessary
1 of 1 people found this helpful
You can also give the Popover frame (not the popover button) and object name and then your script can use Go to Object to re-open the popover.
In fact, I'd use two buttons. Button 1 (visible) sorts the records and uses go to object to open the popover. Button2, the popover button, I would hide with the a Hide when Setting of True so that it is always invisible. This will create the illusion that you clicked the popover button, when you did not actually do so.
that is what I am doing
but it´s still a workaround in my eyes.
It took me some time to realize, that the popover isn´t showing up as expected due to this simple sort script step. Therefor I would say: It´s a bug.
I have not suggested that this is or is not a bug--just provided a pair of options for getting the results that you need. Whether something is considered a bug is up to the FM Inc. personnel.
Thank you for your posts.
Another user (not on the forum) has reported this issue. At this time, any field that is active/selected when Sort Records is activated will have the focus removed from the field. This also includes active popovers.
I have attached your post to the original report. When more information becomes available, I will let you know.
This solved my problem too.
For some reason, running a dynamic portal search started closing the popover after every triggered sort. Adding GoToObject (named portal frame) at the end of the triggered script kept the popover from closing.
Why would this behavior only occur in one of the three dynamic portals I have in this DB? Weird, no?