Hi Scott,

Is there any way to avoid needing that separate AJAX request per row? I dont know much about the source data, but if it's SQL based, could you end up w/ a query that joins in the container-related information? If you do need this second AJAX call, it seems like it would be better to do the first query, process it, then do a single second request that gets the other information all at once.

It would help to know more about the application, but it may not be worth digging this deeply into the store. You could in theory do 1 request to get the initial JSON, do whatever conversion you need, then create a simple ArrayStore or JsonStore with the result. If you plan to do commits then the store/proxy/reader is probably your best option. if you're just reading then I think it may not be worth it.