[SalesForce] Qualified API Name returns null in Test context for Custom Metadata

Winter 19 release provides ability to instantiate the custom metadata in apex .This seems to be useful to generate data for test classes .

However when we have metadata relationship entity or field entity relationship the QualifiedName comes as null in Test class .

Lets take an example with the below code in a Test class .For now use execute Anonymous via Dev console

Relationship__mdt relationship = new Relationship__mdt(
        DeveloperName = 'Test',
        Active__c = true,
        Object__c = 'Account',
        AccountRelationship__c = 'ParentId'
    );
 system.debug('###'+relationship.Object__r.qualifiedAPIName);

In the above code Object__c is of type metadataRelationship (Object definition ) and AccountRelationship__c is also of metadataRelationship type (Field Entity Definition) .

When i do relationship.Object__r.QualifiedAPIName in test context I receive null and not 'Account'.

Similarly when i do relationship.AccountRelationship__r.QualifiedAPIName in test context I receive null and not ParentId .

This makes it not helpful again for use cases where metadata data has entity relationship and the code uses QualifiedName .

Is it a bug or I am overlooking something ?

Best Answer

You still need to use JSON construction if you want to set parent attributes without a true query for the records.

Non Functional Code

EntityDefinition sourceObject = [SELECT QualifiedApiName FROM EntityDefinition LIMIT 1];
MyMapping__mdt mapping = new MyMapping__mdt(
    Source_Object__r = sourceObject
);

Error

Field is not writeable: MyMapping__mdt.Source_Object__r

Functional Code

Map<String, Object> mockMapping = new Map<String, Object>
{
    'attributes' => new Map<String, Object>
    {
        'type' => 'MyMapping__mdt '
    },
    'Source_Object__r' => new Map<String, Object>
    {
        'attributes' => new Map<String, Object>
        {
            'type' => 'EntityDefinition'
        },
        'QualifiedApiName' => 'Account'
    }
};
MyMapping__mdt mapping = (MyMapping__mdt)JSON.deserialize(
    JSON.serialize(mockMapping), MyMapping__mdt.class
);
system.debug(mapping.Source_Object__r.QualifiedApiName);

Log

Account

Related Solutions

[SalesForce] Account Reference returning null value causing and causing ‘Owner Cannot Be Blank’

Relationship fields - ones that end in __r - are not populated in triggers. They are only populated when you perform explicit relationship queries.

So yes you will need to query for the Account.OwnerId values using the Account ID values in the Lead.Account__c field. The resulting method would look something like this:

public static void companyLeadAccountChange (list<Lead> company,
        map<Id, Lead> mapCompany) {
    Set<Id> accountIds = new Set<Id>();
    Lead[] leads = new Lead[] {};
    Id clientRtId = Util.getRecordTypeId('Lead','Client');
    For(Lead l : company){
        If(l.recordTypeId == clientRtId && ...){
            accountIds.add(l.Account__c);
            leads.add(l);
        }
    }
    If (accountIds.size() > 0) {
        Map<Id, Account> accounts = new Map<Id, Account>([
                select OwnerId
                from Account
                where Id in :accountIds
                ]);
        For(Lead l : leads) {
            l.OwnerId = accounts.get(l.Account__c).OwnerId;
        }
    }
}

[SalesForce] Before Insert: Using __r to pull related data in a Trigger.New for loop results in nulls even though lookup relationship has Id

You need to query for the parent records in order to get this information.

Set<Id> parentIds = new Set<Id>();
for (Child__c newRecord : trigger.new)
    parentIds.add(newRecord.Parent__c);
Map<Id, Parent__c> parents = new Map<Id, Parent__c>([
    SELECT Name FROM Parent__c WHERE Id IN :parentids
]);

Now you can loop through newList and figure out the corresponding parent record.

for(zqu__QuoteCharge__c quoteCharge: newList)
{
    zqu__ProductRatePlanCharge__c parent =
        parents.get(quoteCharge.zqu__ProductRatePlanCharge__c);
}

You actually have an issue with your logic that the above will not fix. If you insert sibling records with the same parent, their sum might be greater than the allowed maximum. You also need to factor in siblings already in the database. It should be something more like:

public static void validateMaximum(List<Child__c> newRecords)
{
    Map<Id, Decimal> parentToQuantity = new Map<Id, Decimal>();
    for (Child__c newRecord : newRecords)
    {
        if (!parentToQuantity.containsKey(newRecord.Parent__c))
            parentToQuantity.put(newRecord.Parent__c, 0);
        parentToQuantity.get(newRecord.Parent__c) += newRecord.Quantity__c;
    }
    // now you have the totals from the trigger context

    Map<Id, Parent__c> parents = new Map<Id, Parent__c>([
        SELECT Maximum__c, (SELECT Quantity__c FROM Children__r)
        WHERE Id IN :parentToQuantity.keySet()
    ];
    for (Parent__c parent : parents.values())
        for (Child__c child : parent.Children__r)
            parentToQuantity.get(parent.Id) += child.Quantity__c;
    // now you have a comprehensive total including existing values

    for (Child__c newRecord : newRecords)
    {
        Parent__c parent = parents.get(newRecord.Parent__c);
        if (parentToQuantity.get(parent.Id) > parent.Maximum__c)
            newRecord.addError('message');
    }
}

Best Answer

Related Solutions

[SalesForce] Account Reference returning null value causing and causing ‘Owner Cannot Be Blank’

[SalesForce] Before Insert: Using __r to pull related data in a Trigger.New for loop results in nulls even though lookup relationship has Id

Related Topic