Skip to main content
Emilien Aubertin
New Member
Nov 1, 2026 6:36 PM UTC
Question

Variable mode picker lists collections in random order in the library source file, but sorted in consumer files

Context: variable collections in the mode picker (Design panel > Page / Frame > Apply variable mode)

In a consumer file that uses my published library, the collections in the variable mode picker are neatly organized. In the source file where the library is authored, the same picker lists the same collections in an order I cannot control. The file I use every day to build and maintain the system is the one where this picker is the hardest to use.

The source file has 136 collections, most of them with between 2 and 10 modes. Finding a collection in this picker means scrolling through an unsorted list each time. The variables panel in the same file sorts collections alphabetically. The picker does not follow that order, the creation order, or any other order I can identify.

What I tested, in a blank draft file created through the Plugin API:

  1. Created collection "z", waited about 8 seconds, created "a", waited about 10 seconds, created "m". Each was created in a separate operation and has 2 modes and 1 variable.
  2. Three seconds later, created "lot-1" to "lot-8" in a single operation.
  3. getLocalVariableCollectionsAsync returns them in creation order: z, a, m, lot-1 ... lot-8. Their IDs follow the same order (VariableCollectionId:1:2 to 1:22).
  4. The page's variable mode picker shows: lot-5, a, m, lot-3, lot-4, lot-2, lot-7, lot-1, lot-8, lot-6, z.

That order is not creation order, not alphabetical, not ID order, and not collection key order. Spacing out the creations made no difference: "z", created alone and 20 seconds before the others, comes last. I rebuilt my library in a new file three times to get a clean order, and none of it had any effect on this picker. Nothing in the API or the UI lets an author set this order.

Expected: in the source file, the mode picker should use the same order as the variables panel (alphabetical) or the same order a consumer file shows for the library. Collections should also be reorderable, with that order respected everywhere the collections are listed.

Impact: any library with many collections and modes is hard to work with in its own source file, which is exactly where the author needs the picker most.