And for the second question, no, the URL can change anytime without any notice... the

url.resolveRecord

should be consistent...

agreed the resolveRecord is a better approach, issue is iterating over many many lines for some reason this API call takes quite a while to return, so was just looking for a workaround

try memoizing / caching its value within the same script execution

unfamiliar with

baserecordtype

is that an undocumented search column to get via script?

What is your use case? what are you doing exactly that you need that many calls to

resolveRecord

...

it is creating a dynamic sublist with many lines from search results. I like @jkabot idea though, can't believe I didn't think of that