Why does SOQL return related records when run directly but not when run with Apex

apexsoql

I have a SOQL query that looks like this:

SELECT Id, OwnerId, IsDeleted, AboutThirtyFieldsTotal__c, ...
(SELECT Id, IsDeleted, OverFiftyFields__c, ...
 FROM Borrowers__r )
FROM Loan__c WHERE LSC__c = '0051F00000ocJMdQAM'
ORDER BY CreatedDate LIMIT 200

The entire query is about 1,500 characters long.

When I run this query directly (by selecting it in VS Code and executing it with the command pallet) I get the correct result, with columns for Borrowers__r.FirstName__c with multiple rows for each of the related records.

If I run the exact same query from within Database.query, I don't get the related data, only the data from Loan__c with no data after the last field in the outer SELECT?

Why do I get related data when I directly execute the SOQL but not when it's executed by Apex?

Best Answer

When you debug an SObject record, the output is not necessarily going to show you everything in memory, as it coerces the complex data type into a String to render.

What you observe when you system.debug(someRecord) in this case is incomplete. If you were to system.debug(someRecord.Parent__r.Field__c, you would see these fields are in fact populated.

Alternatively, you can system.debug(JSON.serialize(someRecord)) and see a more complete representation.

Related Solutions

[SalesForce] Fetching records with SOQL in batch apex

The original result set is cached and thus your records have the original state... As explained here http://blogs.developerforce.com/engineering/2013/02/force-com-batch-apex-and-large-data-volumes.html

1) The start method of a batch Apex class collects the records or objects that will be processed.
2) The execute method picks up batches of these records and does the bulk of the processing.

[SalesForce] Why does this SOQL statement return no results

Test methods do not have access to pre-existing data in your Org unless you use @IsTest(SeeAllData=true). I would not recommend this though as if you are dependant on certain data being available then your tests may not passed when moved to another Org.

To fix this you need to create some data within your tests, e.g.:

MyTable testMyTable = new MyTable();
insert testMyTable;

This also makes it easier for you to write your asserts as you know exactly what data you should be testing against rather than relying on the correct data being in the Org you are testing on, e.g.:

MyTable testMyTable = new MyTable();
testMyTable.MyField = 'Test';
insert testMyTable;

System.assertEquals('Test', testMyTable.MyField);

The documentation covers this here.

Starting with Apex code saved using Salesforce.com API version 24.0 and later, test methods don’t have access by default to pre-existing data in the organization, such as standard objects, custom objects, and custom settings data, and can only access data that they create. However, objects that are used to manage your organization or metadata objects can still be accessed in your tests such as:

User

Profile

Organization

AsyncApexJob

CronTrigger

RecordType

ApexClass

ApexTrigger

ApexComponent

ApexPage

Best Answer

Related Solutions

[SalesForce] Fetching records with SOQL in batch apex

[SalesForce] Why does this SOQL statement return no results

Related Topic