However, there is a Memento User who has posted in this forum about using a template to load, among other things, choice field items. I suggest you search in this forum for some combination of "items" and "template" and maybe "load", and you'll likely find his/her posts about the technique. I'm sorry I forgot who posted it.
This reads like it might be the solution
However, this does not address the issue in this thread; what was requested is to load not library field values, but choice field items. Autofill will not assist in accomplishing that.
I tried your previous link, but it took me nowhere. I think that guy was parsing the encoded template file and extracting metadata -- pretty far out there, if you ask me -- but it could provide a solution for this thread.
The name I forgot was Coucinha Palavrante. Read the discussion at...
All I could find is the pissibility of Coucinha Palavrante writing a parser to achieve this?? Whatever a parser is :-) There is actually no non-programming way or inthe Memento interface to do it
Where the parser comes in is that, if you know the format and how to manipulate it to do what you want, you could write a program to find your way around inside a template file and automatically create the choice items you want. So, if Coucinha told me the format in detail, I could probably write such a parser, but we didn't do that, and it isn't a good use of our time, since the format of a template file could change with mobile edition 5.0. This is all reverse-engineering of undocumented stuff.
Now, risking being a little religious, one could imagine programmatically creating your own choice items, your own fields, your own relationships, and thus your own libraries at will. This is all called metadata. But in my opinion, programmatically computing and/or setting FIELD VALUES (data) makes sense, while changing the DATABASE STRUCTURE (metadata) pragmatically is not really wise. Of course, you may disagree with that.