Salesforce Education Cloud: SOQL Error "No such column" When Querying Application Lookup on ApplicationDecision

Follow these troubleshooting steps to update your query syntax or report type configuration based on how the lookup relationship is constructed in your org.

Step 1: Inspect the Field Configuration

1. Navigate to Setup > Object Manager > Application Decision (ApplicationDecision).

2. Click Fields & Relationships and locate the field labeled Application.

3. Note its exact Field Name (API Name) and Data Type:

   • If it is a standard platform lookup relationship, the field API name typically ends in Id (e.g., ApplicationId), and its relationship name is Application.

   • If it is a custom lookup field created in your org, the API name will end in __c (e.g., Application__c), and its relationship name will be Application__r.

Step 2: Correct your SOQL Relationship Traversal Syntax

Scenario A: Standard Lookup Field (ApplicationId)

If the field is a standard relationship, you must reference the underlying ID field for the ID itself, and use the standard relationship name to traverse fields. However, if the relationship name collides with a compound name entity, explicit pathing is required.

Update your query to select the ID via ApplicationId, and ensure your relationship dot-notation precisely matches the schema documentation for the target object (Individual Application):

/* Correct syntax for standard lookup fields */
SELECT ApplicationId, Application.Name, Application.Banner_Student_Integration__c 
FROM ApplicationDecision 
WHERE DecisionPublishDateTime < TODAY

Note: Ensure your query filters use real fields (e.g., DecisionPublishDateTime) rather than object references like WHERE ApplicationDecision LIKE....

Scenario B: Custom Lookup Field (Application__c)

If step 1 reveals that your field is a custom lookup field (Application__c), you cannot use the Application. prefix to traverse fields. You must use the custom relationship name ending in __r:

/* Correct syntax for custom lookup fields */
SELECT Application__c, Application__r.Name, Application__r.Banner_Student_Integration__c 
FROM ApplicationDecision 
WHERE Decision_Publish_Date_Time__c < TODAY

Step 3: Resolve Reporting Failures (Polymorphic Field Errors)

1. Navigate to Setup > Feature Activation > Report Types (or type Custom Report Types in the Quick Find box).

2. Click New Custom Report Type.

3. Select Application Decisions as the Primary Object, provide a label, and click Next.

4. Once the report type layout is created, click Edit Layout.

5. In the Fields Available for Reports pane, locate and remove any conflicting polymorphic lookup fields or owner fields that are causing the schema confusion.

6. Save the layout.

7. Instruct users to build their reports using this newly created Custom Report Type rather than the standard report type.

Validation

• SOQL Verification: Open the Developer Console > Query Editor, paste your rewritten query from Step 2, and click Execute. The query should complete without errors and populate rows with values from the related custom field (e.g., Banner_Student_Integration__c).

• Report Verification: Run a test report using your new Custom Report Type and confirm that it executes and displays data successfully without returning polymorphic entity errors.