Salesforce developer

Protecting code from configuration

2011-08-26T00:44:00.000-07:00

A few posts back, I talked about how you can use SObject in Apex to treat objects generically. For example rather than getting a field from Opportunity like this:

String name = myOpp.Some_Custom_Field__c;

You can use:

SObject mySObject = Opportunity.getSObjectType().newSObject();

String name = mySObject .get('Some_Custom_Field__c');

Whilst this opens interesting opportunities for code re-use, it can leave you exposed - what if someone changes the field's API name? In the first example, a user wouldn't be allowed to rename the API name field - salesforce.com would pick up that the field was referenced and prevent the change. In the SObject example however, this isn't the case - the field name is actually a string, so the change could be allowed and the first you'll hear of it is when your app starts breaking...

One way around this is to create a class that refers to the field directly, as in the first example. Seems a bit wasteful, to create a class just for this. We'll also need to write unit tests even though we're not really going to use the code.

Unless we skip the first part and just create a test class that refers to the field. Something like:

@istest

private class ConfigCheck {

static testmethod void testField {

Opportunity o = new Opportunity();

o.Some_Custom_Field__c = 'Test value';

}

This idea can be extended for all sorts of uses. My last post covered Record Types and raised the question: "What happens if someone renames a record type?". Write another test that checks for the presence of record types your code is expecting to be there. This won't prevent the record type name being changed, but if something goes wrong and you suspect config changes are to blame, you could run the tests in ConfigCheck to check your code's assumptions against the current configuration to see if anything has changed that will cause your code problems.

Record Types

2011-08-26T00:26:00.000-07:00

The Force.com 201 blog posted a great example of how to query the record type table in salesforce in a way that's considerate toward governor limits - think memoization pattern.

It's a useful technique and I've used it on every major project I've worked on over the last few years. However, there is another way to get record type information. Take the following example:

List oppRecTypes = Opportunity.SObjectType.getDescribe().getRecordTypeInfos();

There are also the following methods:

Map oppRecTypesByID = Opportunity.SObjectType.getDescribe().getRecordTypeInfosByID();

Map oppRecTypesByName = Opportunity.SObjectType.getDescribe().getRecordTypeInfosByName();

These all return RecordTypeInfo objects in some way, shape or form, but without using up one of you SOQL queries! These calls are not without penalty however - instead of a SOQL query, you use up a "record type describe", which you have a hundred of in a transaction on EE. So you'll still want to apply the memoization (cache) pattern explained in the Force.com 201 blog.

There is one other drawback - RecordTypeInfos do not appear to have any reference to the developer name of a record type. Really, both record type names and developer names can be changed pretty easily which could introduce breakage to your code, however developer names are less likely to change in my opinion, so querying the record type table can be a safer option.

Describe, and Schema, and SObject and Oh my! Part 2

2011-02-09T15:19:00.000-08:00

In my previous post, I talked about using Schema, SObject and Describe objects to help make code generic and usable across different types of objects. To recap: when creating/updating/deleting an object, a corresponding object should be created/updated/deleted with a small sub-set of details copied across to the new record. The previous post looked at how to automatically determine the type of object should be created (or edited or deleted – I'm sure you get the idea by now) when a record is inserted.

So we have a way of working out what type of object we need to create. How do we go about copying values between the different types of object? As different objects have different fields, we need a way of knowing which fields to copy for which objects. Once again we turn to our good friend Map:

Map<String, Map<String, String> > fieldsByObjectName =

new Map<String, Map<String, String>> {'Account' => new Map {'Name' => 'Name','OwnerID' => 'Custom_Field1__c', 'ID' => 'Account__c'}};

What an eyesore – but not as difficult as it may first look. We have a map (let's call it the outer map) where the values themselves are a map (inner maps). The inner maps hold the details of what fields should be copied for an object; we can get these values from the outer map by get()ing the values associated with the object name of the object being inserted.

Let's look how that applies to the example above. fieldsByObjectName.get('Account') returns a map of strings, keyed by strings. These hold the fields that should be copied from the account to the custom object, and what the corresponding field is on the custom object.

Usefully, the generic SObject has put() and get() methods to retrieve and set field values. Get() takes a field on an SObject for which the value should be returned; put() takes a field and a value and sets the field to the value given. As we have these values in a collection, we can simply loop over the collection and copy the fields with these methods:

Map<String, String> fieldsToCopy = fieldsByObjectName.get(objectName);

for(String field : fieldsToCopy.keySet()) {

newObject.put(fieldsToCopy.get(field), ourNewObject.get(field));

}

Some relatively straightforward DML plumbing at the end of the code handles inserts/updates of the necessary objects.

So, the end result is code that will extend quite nicely if I need to do this for other objects. I just need to create a new custom object with fields to hold values; update the code to map the object to the new custom object, along with what fields should be copied; and finally add a simple trigger that calls the relevant method depending on the type of operation performed.

So are there any downsides?

Though the code is extendable, I don’t think it’s as easy to read as doing it the long-handed way. There’s a whole discussion to be had about the pros and cons of this, however, I think that it would take someone looking at the code longer to understand this approach than simply having triggers and code for each object.

My solution doesn’t do anything to convert between different field types – not really an issue for what I was doing, but if you had a source field of one type and a destination field of another type, some sort of conversion may need to take place. At this time, I'm not sure how I'd approach that.

Where updates occur to objects, I had to hard code queries to retrieve the objects with the sub-set of details so that I could update them (or delete them in the deletion case). This is because I had a set of IDs to use in the query, and had I constructed a query string, there was no easy way to include them in the string. This did feel as if I was breaking the principle that led me down the route in the first place. However, it was “just” a proof of concept and, more importantly, a learning opportunity for me and all things considered, I’m pretty happy with the end result.

Describe, and Schema, and SObject and Oh my!

2011-02-07T15:16:00.000-08:00

I've seen a few of the cool things that can be done with "describe" information in Apex, and using the Schema and SObjects to handle different objects in a generic fashion, but I only recently had a good opportunity to get my hands on it. It was an interesting exercise, so I thought I'd write up my experiences.

First: the requirement. We wanted to give limited visibility of accounts in some circumstances, and full visibility in others. If a user owns an account or is a member of the account team, he (or she) should see all details; otherwise they should only see the account name and owner.

Sharing rules, field level security, record types and page layouts were options that wouldn't deliver what we wanted: sharing rules would control whether a user could see a record or not, not what they could see on the object. Field level security would limit access to fields for all accounts, not on an account-by-account basis. Record types and page layouts would not work for a reason that would take some time to explain, but seasoned admins/developers can work out for themselves.

So we had to customise – we could have overridden view and edit actions with Visualforce, and some of the upcoming Spring '11 features would take some of the pain away when it comes to controlling what fields display on the page in a config-friendly, no-code-changes-needed way. Personally though, I don't like overriding standard functionality with something that looks, feels and operates in such a similar way.

Instead, we decided to create another object that held only the details that anyone can see (account name and owner) that would be created, updated or deleted when something of interest happened on the account object. The oragnisation wide default for accounts could be set to private, granting access to owners and people above them in the hierarchy (and people added to the account team), whereas the new custom object would be public for all. Search for an account and you’ll either see the new custom object if an account exists, or the custom object and the account (if you are able to see the account).

So why bother with the Describe and Schema objects? We also needed to do the same thing for contacts, and possibly other objects in the future. We could have written specific code for each object but it seemed a shame when the operations were the same over the different objects:

If an account/contact is inserted, create a corresponding custom object record with the necessary details.
If an account/contact is updated, update the corresponding record.
If an account/contact is deleted, delete the corresponding record.

So I created three methods, one for each of those scenarios. Each method took a list (or Map) of SObjects and created/edited/deleted a corresponding record using Schema, SObject and Describe. This was then mixed in with some variables to hold information about what fields need copying for each type of object, as well as what custom objects should be created for an object. The later was accomplished with a Map of Schema.SObjectType to String i.e.:

Map<String, Schema.SObjectType> objectMap = new Map<String, Schema.SObjectType>{'Account' => new Custom_Object__c().getSObjectType()};

My method that creates objects when an account or contact is inserted takes a list of SObjects; how do we work out what object we need to create? Like this:

String objectInsertedType = insertedSObject.getSObjectType().getDescribe().getName();

Schema.SObjectType objectTypeToCreate = objectMap.get(objectInsertedType);

SObject newObject = objectTypeToCreate.newSObject();

In the first line, we get the name of the object being inserted (account or contact in our scenario) as a string, then use that string to get what type of record we should be creating from the Map we created earlier. Finally, we use the newSObject() method on the SObjectType object to give us an instance of the object we need to create. So far we've only done accounts – if an account is inserted, the newObject variable will be a Custom_Object__c object. But we can extend this for other objects by adding to the objectMap; for example if contacts should have records created of an object called Another_Custom_Object__c, we could put that into the map. Then, if a contact is inserted, newObject will be a Another_Custom_Object__c. And that way, we at least don't have duplicated logic that's essentially doing the same thing with a few small changes.

So that was how step 1 of making this functionality as generic as possible for use with different objects – implemented a way of determining what object should be created depending on what was inserted. As this has already turned into a fairly lengthy post, I’ll discuss how to copy values between the fields on the two objects in my next post. I’ll also discuss some of the pros and cons of this approach.

Static boolean variables as "Locks"

2010-09-08T03:46:00.000-07:00

Over 6 months and no new posts, tsk tsk! I'm trying to get back into the habit (though did I ever really have it?) with some - hopefully! - short, sharp posts.

So - do you use static boolean variables to control trigger flow and behaviour? I do - a lot. A common use is when Object A has a trigger that does something to Object B, and Object B has a trigger that does something to Object A. To avoid recursion when you update one, you can use a static boolean to cause the second trigger to return immediately rather than execute it, which causes the first trigger to fire again yadda yadda yadda. Similarly, if you have workflow that will cause an update to a record and you don't want triggers firing a second time, a static boolean does the job.

The advice in this post is simple: I think it's a good idea to keep these variables in a separate class. This is due to recent experiences, when I needed such a static variable in a class. I took the easy route and put it in the same class, and this was OK initially. Later, I needed to access that variable from somewhere else, which was possible, however, in that same class I also had a static code block in the same class that queried the database and set some variables.

Now, just by looking at this variable from outside the class, I was causing queries against the database to happen. I had enough headroom for this at the time but in the long term, it's a potential headache waiting to happen.

The solution is to have a separate class that holds such variables and refer to them from other points of code that need to look at them, rather than have the booleans amongst classes scattered here, there and every where. It'll be easier to manage and is better in the long run.

Too many script statements?

2010-02-05T09:08:00.000-08:00

With any luck, this weekend should be the go-live for the project I mentioned in my last post. It's been an interesting project, and, at the risk of sounding schmaltzy, there have been a lot of lessons learnt (and most of them painfully).

I'll be posting about some of the lessons learned in upcoming posts, but I just wanted to take a moment to an idea I have up on Ideas. The governor limit on script statements has been my main obstacle this time around; I know that it's part of multi-tenancy and working with Salesforce. I don't actually mind operating within those limits, but I do like being able to handle meeting those limits in a sensible way.

The reason that "Too many script statements" is special is that, when hitting other governor limits, you can catch them as exceptions and handle them appropriately - usually displaying an error to the user. However, once you've used too many script statements, you don't have any script statements left to tidy up or present something meaningful to the user.

There are ways around this - not hitting the limit in the first place (not a practical solution this time round), periodically checking how many statements have been used and throwing an exception at a threshold (fiddly, unpredictable and uses script statements!). But a neater solution would be nice.

Feel my pain? Don't mope, promote!

Lookup filter - a cautionary tale

2009-11-25T07:27:00.000-08:00

Apologies for the lack of posts of late - I've been busy coding for a project, and I'm off on holiday for the end of the year, so the pressure is on!

I'm at the "fun" stage of the project where I'm writing my test methods and encountered an unusual problem. We have a custom object, I created some instances of this object and saved them to the database. This object also has an (optional) lookup field to another instance of the same object, so I then tried to update some of the inserted objects with references to other inserted objects.

When running the test code, I was getting an error message along the lines of:

"FIELD_INTEGRITY_EXCEPTION: Value does not exist or does not match filter criteria. Click icon to select a value."

Turns out the error was related to a feature in beta, "Filter on Lookup". To be fair, it wasn't the feature's fault: it was being used incorrectly which was causing the problem, and it wasn't an obvious culprit.

The Idea requests a way to restrict what records are shown when a look up button is pressed. For example, let's say you use the Account object for two types of account, customer and partner. On the Opportunity object, you may want fields related to the customer you are trying to sell to, and the partner you are partnering with on the deal. You want to stop users putting partners in the customer field and vice versa. Sharing rules are no good as you want users to be able to see both type of account. With filter on lookup, users click the lookup button on the customer field, and only see customer accounts, and partner accounts when clicking the partner lookup.

It also stops you manually entering names of accounts that do not meet the filter criteria. It's actually slightly cleverer than this, because whatever way you try to save a record, it will check the related object matches the filter; if it doesn't an error is reported...

Which is where the problem I encountered comes into play: the field I was trying to set in my test method had such a filter set on it, and the filter had been set up incorrectly - it was looking at the wrong field, which hadn't been set by my test code. The result: error! Hope someone finds this useful...

Coming in Winter '10...

2009-08-05T01:52:00.000-07:00

The Official Salesforce Blog has just posted a link to the Ideas that have been chosen for inclusion in the Winter '10 release. The two features that leap out straight away are batch Apex and scheduled Apex - seriously powerful stuff. Take a look to see if there's something that will make your life easier...

Force.com Debug Log Parser

2009-07-27T01:27:00.000-07:00

Have you seen Kyle Peterson's Force.com debug log parser? If you spend time working out how your workflows and Apex code are interacting with each other, you should at least watch the video.

A lot can take place in the background when you interact with Salesforce and tracking what's happening can mean trawling through megabytes of log file. Kyle's log parser gives you a near instant overview of what's happening behind the scenes of your application. Great work.

How do you deal with the complexities of multiple Salesforce features interfering with one another? If you have anything interesting to share, let us know in the comments...

Batch Apex processing

2009-07-24T03:25:00.000-07:00

One of the more interesting feature additions to Salesforce and Force.com had a somewhat muted announcement, slipping out on a blog post on the Force.com blog. The comments on the post show there's a fair amount of interest in such functionality.

And rightly so, as batch Apex processing fills a gap that has required kludges to work around until now.

For those that haven't heard of this feature, it allows Apex code to be run asynchronously over large datasets (it still needs to be clarified if it is 5 million or 50 million). You could look over millions of records and produce statistics for reporting purposes; you could look over records and perform actions on a set of them that are not possible through current functionality. It should mean that any time you want Apex logic to apply to massive (by Salesforce standards) amounts of records, governor limits needn't stand in your way.

However, there are currently two limitations: firstly, though the blog post calls batch Apex one of the "new goodies in Summer '09", it was only released on a limited developer preview - if you've not signed up by now, you'll have to wait for the preview to be extended or for the general release. (Of course, if you're a large enough Salesforce customer, you could always try pestering your account exec...)

The second limitation is that batch jobs can't be scheduled to run, and it's not planned to do so in the initial release. It's on the roadmap apparently, but that's all that's been said so far. If the announcement of this initial functionality is anything to go by, we may not know until it's almost upon us. The comments on the afore-linked blog post contain ideas as to how to work around this for now.

Should you use this new functionality once it's released, even if the lack of scheduling is a pain? My answer would be yes if you can make do with a workaround for now, especially if you're creating new batch jobs for your org. It may be a hassle in the short to medium term but at some point down the line you'll (hopefully) be able to add a schedule relatively easily.

For those currently using workarounds that they'd like to get rid of with batch Apex (e.g. using a batch job on one of your own servers to run Data Loader to extract records and upload them back in just to cause something server side to kick off), consider the workarounds available, and if they can work for you, dip your toe in the water - port some of what you currently do to batch Apex and see how it works for you.

And don't forget to leave a message with how you get on - especially those of you taking part in the developer preview.

Welcome, what's this all about, all that jazz...

2009-07-13T13:21:00.000-07:00

Hello!

In the unlikely event you've stumbled on this page, you may be wondering what it's about. I'll explain.

My day job is as a Salesforce consultant - I've been working with Salesforce and the underlying Force.com platform for little over a year now. Sometimes I stumble on things I think others may find useful, encounter problems others may (have) struggle(d) with, or just want to whinge a little.

Rather than bore friends and family, I thought I'd blog my musings so that it may reach a more suitable audience who may actually find my posts useful/interesting/ridiculous, delete as appropriate really.

Obviously it's early days so there's nothing here yet, but I've had a few things I've wanted to share for a little while so hopefully there'll be some content worth reading RSN.