How to pass data to a view model in a linked component?

[marc.fearby]

I've created a panel with its own view model/controller that I've linked to another form (by drag and drop in Sencha Architect 3.2). How do I go about binding values from the view model of the parent form so that the linked panel can see them? I don't even know where to begin tackling this one. Here's my linked component config on the parent form:

{
    xtype: 'fieldset',
    layout: 'auto',
    title: 'Submit to Supervisor',
    items: [
        {
            xtype: 'approvalpanel', // this is the userAlias of the linked component
            width: 450
        }
    ]
}

I need the get the value of a field from a linked model instance of the parent form, from within the 'approvalpanel' and use that value to change the URL of a store's proxy.

[marc.fearby]

I didn't fully appreciate that child components get to see stuff from their parent view models automatically. I was able to do this in the linked component's afterRender() event:

var vm = this,
    store = vm.getStore('Managers'),
    proxy = store.getProxy(),
    record = vm.getData().record, // this is the linked record from the parent form
    user_guid = (record.phantom) ? App.global.user_guid : record.get('user_guid');

proxy.url = '../Service/Employees/' + user_guid + '/Managers/';
store.load();

[marc.fearby]

This works well for configuring stores based on a value in the parent view model, but now I've hit another bit of a snag. I want to set a field in a linked record of the parent view model when the combobox selected value changes in the linked component. I could probably do this in the linked component, but that's hard-coding a value in the parent record/field that I don't want to do:

this.get('linkedRecordNameInParent').set('fieldName', 'value');

The whole reason I created the component separately was so that I could use it in several places without it having to know the name of the linked record and field in which to set the selected value from the combobox.

What's the "correct way" to handle this? Is there a way the parent component can look for a common reference/binding/whatever and use that to set the value of a field in a linked record?


Being a Sencha Architect thread, I'm probably having a conversation with myself, but I'll try my luck.

[bogc]

Did you ever find an answer to your last post?

[marc.fearby]

Did you ever find an answer to your last post?

It's been a while now but I think I ended up just compromising and going with a hard-coded reference and made sure I added comments where ever I used it to inform any other poor soul who might have to look at my code one day. I had plans to really abstract that particular component and re-use it everywhere but I decided against that, given that hard-coding I would have needed.

Having said that, now that I think about it some more, I suppose might be able to viewmodel.set() a property which exists in the parent view model (and not in the child), and it might therefore end up setting it higher up where it belongs rather than creating it on-the-fly in the child/linked component?