If you include the related records list instead of the table portion inside any of those select style formulas, the system will only run the select function over the records inside that list.
So say I’ve got a database of 300,000 records, but the related records for a specific individual record amounts to only five.
If I use the related records formula part, the select function only operates over the five records instead of the 300,000.
It can be tricky to get it to work sometimes, syntax and all of that… But when it works it really speeds up your app and increases the efficiency.
You know what guys, thank you for all the help, but it took me FOREVER to get the related refs to show up in the app exactly how I wanted them, and tinkering with all this stuff makes me nervous so I’m just going to order my lists in Drive alphabetically to achieve this end instead of messing with the app.
(replacing key-column with the name of the key column of the Recipe Plant Merge Table table)
In order to successfully use any of the above with ORDERBY(), The Plant column of the Recipe Plant Merge Table table must be of type Ref and refer to the Plant Information table.
If you’re trying to order row in a view, that can only be done from the view configuration. Ordering the list of rows given by REF_ROWS() will in no way affect the order the rows are presented in a view.