well, unfortunately, it seems that it is dependent on the amount of records on the Search step. I was able to use the max|attribute='id' no problem when i tested on a very simple app but when i tried it on an app with larger data, it gave me the same error:
Query step produced too many items too allow inline indexed access. Please use a LOOP construct.
I assume it has something to do with the way results are paginated?
Anyway, just in case you had another thought:
My use case was to do a Search step and for each of those records, I want it to update two fields. For one of those fields, i only wanted it to update when it was the last iteration of the loop.
What I ended up doing is: outside of the for loop, I went with a Make A Request step that queries the table with the same conditions as my Search step and then from a discussion that you were also a part of, i take the highest record id from there (since my table settings is sorted by Record ID - low to high) and then just use look up and update the record.
thank you for your help and insights!
------------------------------
Tim D
------------------------------