[Request] update ability macros to include the id's of repeating rows

Is it possible write a script that can review a sheet's ability macros to learn the id's of repeating items and rewrite the macro substituting their appropriate id? Problem: Currently, many sheets have ability macros that use the old repeating row naming schema "repeating_foo_X_..."  where X is the row number.  This will no longer work since the new naming schema requires including " $ " in front of the row number or use the row's id.  The " $ " still seems "generic" in nature and with the Devs eluding to the ability to re-order/arrange repeating rows in the future wouldn't it be better to use a rows id?

If you're worried about future-proof against re-ordering repeating items, I think you're out of luck. I'm fairly confident that findObjs will return things in the order they were created.

I think Vince is talking about the Repeating Row ID, not the Attribute ID. So, something that could work is adding a hidden field to the Repeating Row named index, then using sheet workers to fill in the row number.  Based on my testing, the getSectionIDs() function returns the rows in the correct order.  You could then find all of the repeating attributes named index and use them to create a map between Row ID and Row Index, then grab all the repeating attributes, build a map form repeating_<foo>_<index>_<bar> to repeating_<foo>_<id>_<bar>, then do a string replace in each of the macro and ability action properties. Honestly, it wouldn't be too hard with that hidden index field.

sheetworkers can't see ability macros, correct? only attributes? if that is true: we might have to use the API to rewrite the ability macros.  At least it finally looks like we can select fields out of repeating sections, for some reason it was not working for us before. We can add hidden fields to the repeating sections, as Aaron suggests, and store the row ID in there, that way the API can easily access the id of a row to generate a string to search and replace in macros. Which may be easier for people with hundreds of monsters to update. The hidden field could be called @{Row_ID} or something, and the sheetworker could update it on creation of a new row. in the sheet:opened event on an old sheet it would just loop through all the repeating sections and set those hidden fields.

Actually, what you'd need to store is the row index number (1,2,3,...). The API can see the row IDs in the names of the repeating attributes, but it doesn't know which one is which by index. 

Brian said: If you're worried about future-proof against re-ordering repeating items, I think you're out of luck. I'm fairly confident that findObjs will return things in the order they were created. (Side topic:  Then the first player found by findObjs would always be the campaign creator.... just saying. Always thought that would be useful i.e. a "permission" system.)