Loading nested data into two different stores

[poweranimal]

I have two models that are related. One is called 'Changes' and belongsTo a 'Configuration'. This is how I've defined the association on a 'Change':

associations: [{
            type:'belongsTo', 
            model:'Changes.model.Configuration',
            primaryKey: 'id',
            foreignKey: 'configuration_id',
            associationKey: 'configurations'
        }],

On the changes store I have a proxy defined like this:

proxy: {
            type: 'ajax',
            url: 'services/changes.php',
            reader: {
                type: 'json',
                rootProperty: 'changes'
            }
       },

When the store is loaded it is passed a JSON object that looks like this:

{
    "success": true,
    "changes": [
        {
            "id": 1,
            "changeId": "CMS19178263",
            "briefDescription": "Loaded from Proxy!!!",
            "configuration_id": 3,
            "configurations": [
                {
                    "id": "3",
                    "longName": "002669-2669-abc_-_windows_7_desktop.Computer.Windows",
                    "ciName": "002669-2669-abc_-_windows_7_desktop"
                }
            ]
        }
    ]
}

When the record gets loaded I can call 'record.getConfiguration()' but all of the fields in 'data' show null (except id shows: ext-record-9). Inside the raw array there is one object that shows all of the fields with the data loaded from the JSON. Can anyone see why the data isn't being read into a new Configuration object and saved to the Configuration store?

Let me know if I need to post anymore information...

[mitchellsimoens]

Try making the configurations property value an object instead of an array in your JSON.

[poweranimal]

Doing that made it so the configuration showed up as an associated object of the change. But it doesn't load it into the configuration store. Now I'm thinking it's going to be better to load the two stores separately (with flat instead of nested JSON). But will the change objects get automatically associated with their respective configuration objects if the associations definitions are setup correctly on each model? Or is that not a feature built into the framework?

Try making the configurations property value an object instead of an array in your JSON.