Oh my god. It's full of code!

Lightning Update List of Records Workaround (Quick Fix)

I’ve been doing some work with Salesforce Lightning, and so far it is certainly proving… challenging. I ran into an issue the other day to which I could find no obvious solution. I was attempting to pass a set of records from my javascript controller to the Apex controller for upsert. However it was throwing an error about ‘upsert not allowed on generic sObject list’ or something of that nature when the list of sObjects was in-fact defined as a specific type. After messing around with some various attempts at casting the list and modifying objects in the javascript controller before passing to the apex to have types I couldn’t find an elegant solution. Instead I found a workaround of simply creating a new list of the proper object type and adding the passed in records to it. I feel like there is probably a ‘proper’ way to make this work, but it works for me, so I figured I’d share.

//***************** Helper *************************//
	saveMappingFields : function(component,fieldObjects,callback)

        var action = component.get("c.saveMappingFields");
            fieldObjects: fieldObjects
        action.setCallback(this, function(actionResult){
            if (typeof callback === "function") {
//**************** Apex Controller **********************//
global static string saveMappingFields(list<Mapping_Field__c> fieldObjects)
	list<database.upsertResult> saveFieldResults = database.upsert(fieldObjects,false);	

global static string saveMappingFields(list<Mapping_Field__c> fieldObjects)
	list<Mapping_Field__c> fixedMappingFields = new list<Mapping_Field__c>(fieldObjects);
	list<database.upsertResult> saveFieldResults = database.upsert(fixedMappingFields,false);	

2 responses

  1. Hi Dan,

    Curious, in your helper javascript when setting up the action to enqueue, do the JS objects in your ‘fieldObjects’ array have the property ‘sobjectType’ : ‘Mapping_Field__c’ ?

    I’ve found that during the Salesforce JSON deserialization on the Apex side tends to fail without the JSON objects explicitly stating their sobjectType.

    Hope that helps! Otherwise, good to know that re-creating the list works too.


    December 3, 2016 at 5:34 am

    • I did, and do have the property set. Maybe I did so incorrectly. Setting that seems to work for a single sObject, but sending a list of them doesn’t.

      December 8, 2016 at 11:00 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s