Model with a subquery condition and a subcondition migrated incorrectly to version 11.2.9

Here’s a sample page, with console messages displaying the change to the SOQL:

You may need to play with the subcondition itself. The subquery as I defined it will list our earliest Apex Class authors. When the SOQL “breaks,” it lists all our Apex Class authors. But you will see the SOQL change regardless of the user records actually retrieved, or not.

Hey Mike! I was wondering if you’d be able to grant Skuid login to be able to see what you’re seeing here. When I copy the XML onto the page in 11.2.11, I’m not seeing anything strange in the console. I see this:

I don’t believe I’m fully understanding the repro. With clearer steps to repro or perhaps more insight into what you’re seeing, I might be able to be useful for a change.
Let me know.

I see a couple of differences on your console.

1st is the “on re-query” display happening before page load. I don’t think I’ve seen a model Action “when Model requeried” triggered on the initial load. It’s not happening for me.

Secondly, none of your SOQL statements include the subquery condition "…xClass WHERE ((CREATEDDATE<LAST_N_YEARS:3)))) LIM… (Line 9 in the xml).

I loaded the xml from the post above into a new page today and I get this:

This is what that subcondition looks like in the composer:

As to access, I’m not certain exactly how to do that, or more importantly, if I have the authority to do so given our confidentiality constraints. The Admin I need to talk to, unfortunately, is out until Dec 5.

Mike,

I think you may be creating your sub condition incorrectly. The field ‘Subcondition Logic’ is used to define how to apply the sub conditions. It would normally look like this-> 1 OR 2

I modified your page slightly and added the sub query condition. Here is what i see:

Here is the modified page. It does show the same query applied on page load and after clicking the query button.

    
        
            
                
                
            
            
                

    


            
            
                
                    
                        
                    
                    
                        models.loaded
                    
                
            
        
    
    
        
            
                
                
            
            
                
                
            
            
                
                
            
            
                
            
            
                
                    
                        
                    
                
            
        
    
    
        
        
            (function(skuid){
var $ = skuid.$;
$(document.body).one('pageload',function()
{
        console.log("Query on page load:")
        console.log(skuid.model.getModel("Users").soql);
    }
    );
})(skuid);
            console.log("on re-query:")
console.log(skuid.model.getModel("Users").soql);
        
        
        
    
    
        
    

```
Thanks,

Bill

Thanks, Bill. But that was the point of the post, that the subcondition logic moved on an upgrade, and the page quit working correctly.

Mike,

My mistake!  I understand what is happening.

I think Skuid needs to do the following to reproduce this issue:

1. Create a new developer org.
2. Install an older version of Skuid (11.2.4).
3. Install your sample page.  Verify that it works.
4. Update Skuid to 11.2.9.
5. View your page and see if it ran into the same issue with migrating the sub-query condition.

Yes. Agreed! The post was also submitted as an FYI for anyone else who might encounter the same symptoms.