View Full Version : Unable to load data in Architect (preview) when using a MemoryProxy

18 Dec 2012, 4:17 AM
REQUIRED INFORMATION Architect Build tested:

Build: 676

Project Type:ExtJS 4.x Description:

When a MemoryProxy is used, the option on the store
context menu to 'Load data' is disabled (see screenshot).
The problem does not occur when no proxy is used (data entered
into the 'data' property of the store) or if an ajax proxy is
used. The resulting code works and the data is shown in a grid
at run-time just not at design-time.

Steps to reproduce the problem:

Create a store and select a model
Add a memory property and add a Json reader
Enter data into the 'data' property of the memory proxy
Click on the store using the right mouse button to see the
context menu and the disabled option.

The result that was expected:

The option would not be disabled

Screenshot, Project, or Video:


Operating System:

I'm using Win 7

18 Dec 2012, 8:41 AM
When passing in the data configuration, the Store should automatically load it... there really isn't an option to "load".

Are you not seeing the contents of whats loaded in what you have it bound to?

18 Dec 2012, 9:26 AM
I see the data at run-time but not at design-time. I'd like to be able to see the data at design time just as I can see the data accessed from a different proxy. I want to be able to use the memory proxy so I'm able to use a json reader.

I've assumed I'm not seeing data in the grid at design-time because I can't load it. Maybe that's not right and maybe I'll need to revert to using the store's own data property. When I use the store's data property the data *is* shown in the grid at design-time but, as I recall, uses an array proxy.

So why use a memory source you might ask. Well the data is coming from an in-memory feed (this is the use of a browser as an embedded application) and it's much easier and faster to poke the data into a function (using InvokeScript) which in turn calls store.loadData() than it is to arrange some in-application web service the browser can access so I'm able to use a json proxy.