[SalesForce] SOQL not displaying all the fields requested (relation fields)

I am not sure if I am missing something but I am doing the query below and for some reason it is not displaying in the result the relationship fields requested, while when I do it from the developer console it works fine.

My query looks like this:

registrations = [Select Id, Name, miiEventV1__Status__c, miiEventV1__Client__r.Name, miiEventV1__Client__r.PersonMobilePhone, miiEventV1__Client__r.PersonEmail, miiEventV1__Client__r.PersonHomePhone,miiEventV1__Client__r.Email_Subscriptions__c ,miiEventV1__Client__r.Client_Manager__c From miiEventV1__Registration__c LIMIT 1];

My debug log looks like this:

system.debug('@@@@'+registrations);
displays:
DEBUG|manza(miiEventV1__Registration__c:{Name=REG0016109, RecordTypeId=01290000000G2OOAA0, miiEventV1__Client__c=001N000000LnHirIAF, Id=a0AN0000002s1SDMAY, miiEventV1__Status__c=Registered})

In the developer console:
enter image description here

I dont understand what is happening, why the debug log is not getting the fields miiEventV1__Client__r…?

Best Answer

The debug logs will only show the Foreign Key when you debug the sObject like you have.

If you

system.debug(registrations. miiEventV1__Client__r.Name);

You Should See the name being output.

Related Solutions

[SalesForce] SOQL results returning RecordTypeId which is not included in query

In Apex Code, the SOQL engine automatically includes RecordTypeId and Id in any query result, even if you don't ask for it. There are a few other hidden parameters that appear in a query when presented to the SOQL engine.

For example, if you don't include a LIMIT statement, or set it to higher than 1+Limits.getLimitQueryRows()-Limits.getQueryRows(), the system automatically adds or changes the limit to LIMIT :1+Limits.getLimitQueryRows()-Limits.getQueryRows(). This is how the governor limits are enforced. The exception to this is for Batchable classes that use a Database.getQueryLocator statement, where the limit is set 50,000,001 rows. Also, when you don't specify ALL ROWS, Apex Code silently includes a filter IsDeleted = FALSE. In other words, whatever you put into your code isn't necessarily what will be executed by the SOQL engine.

Note that this means the following two queries are (approximately) the same in Apex Code:

Account[] accounts1 = [SELECT Id, RecordTypeId, Name, (SELECT Id, RecordType, Name FROM Contacts WHERE IsDeleted = FALSE) FROM Account WHERE IsDeleted = FALSE LIMIT :1+Limits.getLimitQueryRows()-Limits.getQueryRows()];
Account[] accounts2 = [SELECT Name, (SELECT Name FROM Contacts) FROM Account];

I don't know if there's a documented reason why RecordTypeId was specifically included, while audit fields were not, but I seem to recall that this behavior did not always exist in Apex Code, which suggests to me that some new SObject method was added that required this field to be present to function correctly. My best guess is that this field was needed for the Visualforce runtime engine to correctly render dynamic picklists on records.

[SalesForce] Picklists not Supported in SOQL WHERE Clause (External Objects)

I suspect this might be down to how they're implemented on the external system itself. The where part of the query is not handled by Salesforce, but by the OData compliant API at the other end, the where basically defines a query for the REST response.

Dynamics CRM uses text based labels for what we know as picklists, but then has integers for the actual values stored in the database; so I suspect what is happening is that Salesforce doesn't allow such queries to be made because implementation details would vary. If Salesforce sends a text value to Dynamics that's not going to match on the other end, and I don't believe Salesforce have processing in place to import such values from the other system when configuring the object.

I could be completely wrong of course :)

Best Answer

Related Solutions

[SalesForce] SOQL results returning RecordTypeId which is not included in query

[SalesForce] Picklists not Supported in SOQL WHERE Clause (External Objects)

Related Topic