circular reference with 2 listeners

Hi Greg,

Actually, I don’t think that these 2 listeners create a circular loop, because updateData() does not cause handleSave() to be called. Here’s the way that the Model API methods work with Editors:

model.save() –> once the operation finishes, handleSave() is called on registered Editors
model.cancel() –> once the operation finishes, handleCancel() is called on all registered Editors
model.updateData() –> once the operation finishes, handleDataRefresh() is called on all registered Editors

So, when your FleetQuote save listener gets called, it will go call updateData() on the FleetSectors Model, which basically requeries for data in that Model. This does not trigger the handleSave() on your FleetSectors listener. 

That being said, perhaps there’s some other stuff going on in your page that I don’t know about, so to give you the benefit of the doubt, here’s how you can test: add console.log() statements in your handleSave() methods to see whether they get continuously called, like this:

listener.handleSave = function() { 
console.log(‘fleet quote listener handleSave called’);
if (!FleetQuote.hasChanged) { 
console.log(‘requerying Fleet Quote Sectors’);
FleetQuoteSectors.updateData(); 
} 
}; 
listener.registerModel(FleetQuote); 
}); 


listener.handleSave = function() { 
console.log(‘sectors listener handleSave called’);
if (!FleetQuoteSectors.hasChanged) { 
console.log(‘requerying Fleet Quote’);
FleetQuote.updateData(); 
} 
}; 
listener.registerModel(FleetQuoteSectors); 
}); 


If you see these statements continuously show up in the JavaScript console, you’ve got a problem.

All that being said, there are ways to listen for changes on particular fields in a Model – are you thinking that you’d want this to happen before the Quote model is saved (e.g. real-time) or only after it is saved?

Hi Zach, as you suggested, it only executes once (console screenshot attached),
but what does happen is the ‘Sector’ row disappears when I hit save. (this was happening before but I didn’t mention it as I thought fixing the listener would resolve this.)

There is a condition on the sector object which says: 

Sector__c records WHERE Fleet_Quote__c
is in the set of values
containing the id field from any row returned by the FleetQuote model
This condition is always on.

(I haven’t used the url id parameter as there is a parent object to both of these, kind of like an opportunity object, which contains the id parameter)

It seems as if the FleetQuote model isn’t refreshing in order to satisfy the condition on the sector object.

If I refresh the page then all is fine - the data put in is rendered correctly in the page, and I’m able to make changes. Its only with a brand new FleetQuote record that the child sector row is disappearing.

I’ve attached another screenshot of the disappeared sector page with console statements.

Models with “Field from another Model” conditions ordinarily won’t “reevaluate” the “Field from another Model” part of such Conditions behavior unless the Source Model is also requeried at the same time — i.e. for your scenario, if you are going to requery the Sectors Model, you’ll have to requery the Quotes Model as well, using

skuid.model.updateData([FleetQuote,FleetQuoteSectors]);

if you want to rely on the Field from another Model Condition to produce your desired behavior. NOTE: querying for the FleetQuote Model first is also essential.

If there’s a way you can write your Conditions so that you don’t have to use the Field from another Model IN Condition here, that might be the way to go — e.g. if you can say Sectors where Fleet_Quote__r.Opportunity__c = (param) Id, that would be an option that would avoid the problem.

IT WORKS!! I hadn’t thought of traversing fields on the condition. The simple fix is often the way to go.

Thank You!!