Search Results

Likely cause is the specific behaviour of the deserialization methods. Try JSON.deserializeUntyped instead: Task taskRecordFromString = (Task) JSON.deserializeUntyped(jsonString); Your JSON.deseriali …

The getType method you are calling directly returns a DisplayType value rather than a String so change your code to: DisplayType displayType = record.getDescribe().fields .getMap() .get(fieldN …

SObjectField f = fieldItems; if (String.isNotBlank(con.get(f))) { existingContact.put(f, con.get(f)); } because the SObjectField can be used directly as Apex has map-like syntax for dynamic access of SObject … See the SObject Class documentation. (JavaScript does offer the syntax you used.) I also removed the assignment of the existingContact value to itself as that seems pointless. …

You can convert the Id value into a record of the correct type (as all instances must have a specific type) and assign the record the Id using this pattern: List<SObject> inserteds = new List<SObject … >(); for (Database.SaveResult result : results) { if (result.isSuccess()) { SObjectType t = result.getId().getSObjectType(); SObject r = t.newSObject(result.getId()) …

I suggest that rather than relying on some utility class, you become familiar with the platform's APIs so you can compose the appropriate solution each time you want to query all the fields, particula …

If you can change the header row to contain the field API names not label text then you can use code like this: String[] headings = filelines[0].split(','); for (Integer i = 1; i < filelines.s …

There are many other methods available too - see SObject Methods. Custom objects all have these Custom Object Standard Fields. … When you have an SObject you can get its SObjectType via its getSObjectType() method. An Id also has a getSObjectType() method. …

* Test.createStub doesn't work for SObject/SObjectType/SObjectField. … = null) return System.hashCode(field); else throw new InvalidStateException(); } } // Equivalent of SObject public class Obj { Type type; SObject o; …

Equality and the hash code value are based on all the properties of the SObject which makes sense. … There is an SObject-specific nasty case: if you put SObjects in a set before they are persisted, persisting them will set an Id in the SObjects and your set will be broken in any following logic. …

.); call at the end: Id id = 'xxxxxxxxxxxxxxx'; SObjectType t = id.getSObjectType(); SObject[] records = Database.query('select Id, Name from ' + t + ' where Id = :id'); System.debug(JSON.serializePretty …

You can use this dynamic access technique (all SObjects support map-like methods): for (Sobject record : kbList) { String stringField = (String) record.get('StringFieldApiName'); ... } to avoid … If you do need type-specific logic, the relatively new switch is a good way to do that: for (Sobject record : kbList) { switch on record { when Faq__kav f { // f is a reference …

So instead create your own mutable (writeable) set: Set<Id> accIds = new Set<Id>(); for(List<sObject> sob: searchList) { Set<Id> tempIds = (new Map<Id,SObject>(sob)).keySet(); accIds.addAll(tempIds … ); } Personally I would write the logic like this: Set<Id> accIds = new Set<Id>(); for(List<sObject> sobs: searchList) { for(sObject sob: sobs) { accIds.add(sob.Id); } } …

You will need to do a separate query for each SObject type with IsDeleted = true in the where clause: there is no "query by any type" mechanism. …

But there are are get methods in the SObject class for this case where the field names can be used in string form: List<sObject> objects = database.query(queryString); for (sObject o : objects) { …

Given that AssetList holds a list of Patent__c objects: Public static List<Patent__c> AssetList; it is pretty unlikely that the following statement and similar statements are correct because lookup …