at first I set one column in my table 1 so that I can link it to items of records from a different table 2 (via multi-linking to record). Then I wish to fill a different column in table 1 through rollup function with another matching item of the same records from table 2. Problem is, that the order inside the rollup column is automatically opposite to the order in the first column linking to the record. I would like to have the same order in both columns, but I cannot set anything about the order connected to the rollup function.
Are you using the ARRAYJOIN(values) or CONCATENATE(values) function for the aggregation function?
I experience the same behavior, the Rollup values are ordered in the opposite order of the multi-link column. I believe we could reach out to the support helpdesk in this case.
I’ve also come across this problem and would like to add my support for a resolution.
I have a related question, what determines the order of items in a multi-link field (and hence the opposite order in a Rollup of that field)? My guess is it seems to be creation date of the linked record, is that correct? It would be great to be able to influence the ordering, with options such as alphabetic, date modified, or matching the order in a view.
I also wish this could be fixed. My use case is for contact info. For example, my linked field will have “John Doe” then “Jane Doe”. Then I’ll have either a rollup or lookup field for their phone numbers and emails. In those rollup/lookup fields, the order of the contact info is for Jane then John instead of John then Jane.
This makes it a bit confusing, especially in page designer when exporting for 3rd parties.
There are two issues here, and both have solutions:
Inconsistent order of linked records in different field types (linked record, vs, formulas, vs lookups). This has been fixed as described in this support article.
Sorting linked records in rollups. The order in the rollup is the same as the order the linked record. You can automatically sort the order using the Batch Update block, as mentioned earlier in this thread. (The main caveat is that linked records can only be sorted one way, so all rollups for the linked record must have the same sort.)
Hi @kuovonne ,
There is still a bug with the Batch Update. I have it sorting the linked records in ascending order (smallest to biggest) but this is an example of it after Batch Update: 10082, 22354, 22355, 8534, 9295, 9296
Expected: 8534, 9295, 9296, 10082, 22354, 22355
As you can tell the first digit for each appears to be in ascending order, but the entire number set are not. I have to correct many of mine manually.
@Stephen_Joslyn It looks like the linked records are being sorted alphabetically when you want a numeric sort. Can you share a screen capture of the primary field of the linked table? It may be that Airtable thinks that your primary field is a text string instead of a number.
The linked records are auto numbers field. I assume that’s numbers, no?
Dr Steve Joslyn BSc BVMS DipECVDI MRCVS MANZCVS
Chief Executive Officer
RCVS, European & Australian Recognised Specialist – Radiology, AI Comittee Co-Chair (ACVR/ECVDI)
address 32/152 St Georges Terrace Perth WA 6000 mobile +61 411 185 530
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error-free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. VetDB is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
@Stephen_Joslyn You are right. I just did some tests and the Batch update app sorts linked records alphabetically, even if they are numbers.
I suspect that this occurs because under the hood, the primary field of a record is stored as a text string in a linked record field, and this text string is being used for the sort. The app does not go back to the original primary field to determine the field type.
I have written an app “Sort Linked Records” that will properly sort linked records. This app is currently in review with Airtable and will eventually be released on the Marketplace, although I do not know when.