Got a record view form, a list view form, and a find FID (consisting of globals).
The Find button on record view takes user to the FID, then search results show list view if n > 1.
Works great AFTER first find, or in any case if n = 1 (showing record view).
However, the first find after solution startup will return ALL records (on list form) if n > 1 regardless of criteria entered.
On the other hand, if after startup I go to list view then back to record view, then a find from record view works as expected.
So, I tried this routine for record view onLoad:
globals.the_usual_onLoad(); [addFoundSetFilterParam, etc.]
forms.record_view.goto_contact_list();
forms.list_view.goto_contact_record();
It works with respect to the initial find, but now unless such a find is conducted, the result is that navigation to that list view reveals a completely blank space (white screen) where the (custom) controller should be.
So, then I tried:
globals.the_usual_onLoad();
forms.record_view.goto_contact_list();
forms.the_custom_controller.controller.show();
forms.list_view.goto_contact_record();
Hey, it works great now. But I can’t help but wonder, why the hoops to jump thru? How can it be accomplished simply?
Further fun:
globals.the_usual_onLoad();
forms.list_view.controller.show();
forms.custom_controller.controller.show();
forms.record_view.controller.show();
Now, this one is really out to lunch. The result is a view of the record view (controller = none) showing the custom controller for the list view! And, when I enter design mode, the list view is what shows up.
So, I have a workable routine here (the second one), but I am not sure why. Or, rather, why the other two do not work.
Any insights?
Jim