System.QueryException: No Such Column - Strange RunAs Behavior with Summer '14?

Question

Question

Is there any known reason a SOQL Query would return a runtime System.QueryException on a custom field in test methods, in particular one one via a parent lookup in a test? I would have thought this is impossible if the apex code compiled. Any one else seeing this sort of behavior?

Background

The simplest case I can get to fail does the following

1. Creates a test user with specific profile and does a runAs call
2. Create a Parent__c record with field Fail__c
3. Create a Child__c record with lookup Parent__c pointing to record from step 2
4. Query that record
5. Query Exception?

Code would look like this

static testmethod void feelsLikeImTakingCrazyPills() {
    system.runAs(generateTestUser()) {
        Parent__c parent = new Parent__c(Fail__c = 'wtf');
        insert parent;
        insert new Child__c(Parent__c = parent.Id);
        List<Child__c> children = [SELECT Parent__r.Fail__c FROM Child__c];
        // System.QueryException: No Such Column 'Fail__c' on entity 'Parent__c'
    }
}

Even more bizarre if I don't populate that field, no issue.

static testmethod void feelsLikeImTakingCrazyPills() {
    system.runAs(generateTestUser()) {
        Parent__c parent = new Parent__c(Fail__c = 'wtf');
        insert parent;
        insert new Child__c(Parent__c = null); // <-- i don't populate the lookup here
        List<Child__c> children = [SELECT Parent__r.Fail__c FROM Child__c];
        // no exception
    }
}

And in the actual code that lead to this, the query is in another class. If I make it without sharing no issue.

WTF

Is anyone else seeing this? Seems so confusing:

• Why would I be able to set a field (in other words it's field level security is read and edit) but not query it?
• Why would it matter whether I populated the field?
• Why would without sharing make a difference?
• Why would a non-dynamic query but not run?
• Am I alone in experiencing this?

Updates

I'm seeing more strange behavior now in the same vein. Trying to create another object, which the test user's profile has perms for, but when I try and insert it I get DML operation INSERT not allowed, works fine for admin.

Answer 1

Ralph -- here is a possible explanation based on a similar experience I had:

If you are generating a SOQL Select in class A using Schema.Describe to get all fields from CustomObject__c resulting in:

Select field1__c, field2__c, field3__c, stdFieldA, stdFieldB  
from CustomOBject__c

Yet, when this query was executed by class B, you get error System.QueryException ‘No such column stdFieldB’

The issue may have to do with versions of each class:

1. Class A, that generated the SOQL from the Schema.Describe was at VX.0
2. Class B, that executed the generated SOQL from the Schema.Describe was at VX-n.0
3. Test Class T, that executed Class A and B was at VX.0

So, the Schema.describe in class A found all the fields known to SFDC version VX.0 which included CustomObject__c.stdFieldB but when executed by a much older class B (version X-n.0), the stdFieldB wasn’t part of the schema at that point in history so QueryException ensued.

Updating class B to VX.0 resolved the issue

Actual use case is blogged here - http://cropredysfdc.com/2014/08/01/versioning-woes-no-such-column-field-is-valid/

Answer 2

Check the deployment status of the object, if it's not set to Deployed you can get this error. It's confusing since the profile permissions look good, but you can't query the object. Note that you can also avoid this issue by adding without sharing to the class which runs the code in system mode which ignores the deployment status.

Gotcha the error can occur on the detail object of a master/detail relationship if the parent is not deployed, so if the object in question is a child object be sure to go up the hierarchy to look for issue with the deployment status

Answer 3

If the user you runAs does not have permissions to the Field, it will throw an error at runtime. However, the apex code (and soql) is still valid which is why the code compiles.

declaring your class as 'without sharing' means that your instance's sharing rules are not enforced

Either fix your sharing rules/permissions or use without sharing.