Hi Pat,

Have you tried setting an action on the parent model (when it is saved) to requery the child model?

You could use the ‘Query Behaviour’ to add rows rather than replace all rows in the model.

In response to your actual question, my understanding of the ‘abort this model’s query’ option is that if the condition doesn’t exist, then you don’t want to query for any data or present any data to the user (otherwise it could return hundreds or thousands unrelated rows which don’t match your condition)

Does that help?

Hey Greg –

Thanks for the response. For “Abort this model’s query” I do follow that if that option is selected, then no data should be queried.

What’s strange to me is that aborting the child relationship’s query aborts the query for the entire model …

It seems like that shouldn’t be aborting the model, just the query on this child relationship.

Basically, I’d expect to see the model data, but nothing queried for this child relationship.

Thoughts on this? Do you think I’m trying to perform some sort of unnatural act?

I’ll admit, I may be putting this model in an awkward situation by referencing another model that only has one unsaved record on page load…

Thanks!

I’m definitely not qualified to give an official answer on it, but I think it might be an unnatural act as you say. It looks like you’ve got the child relationship contained ‘within’ the model, so yes, it aborts the query for the whole model.

I hope I can be proven wrong however and there is a solution here for you somewhere.

I thought I had answered this yesterday.  But no…

Pat’s diagnosis is correct.  When you abort the child relationship subquery if no values are found it aborts the whole model query,  rather than just the subquery part of it.  Right now there is not a declarative way to solve this problem.  And no - I don’t believe this is attempting an unnatural act… 

I’ll post this as a reccomended change in our roadmap. 

Thanks Rob.
So … is there any way to update a Child Relationship’s conditions via Javascript?

Looks like I was able to write a renderer to get me where I needed to go. 
Filtered a related model (filled with the Child records) to display a value in a column on the parent object’s table editor.

Pretty much what was happening with the Child relationship, just set up so it could handle the fact that only 1 of the 3 involved models were saved on page load… (that is, to avoid the “ignore condition” versus “abort model’s query” situation).