Stupid Salesforce Tricks

We use ClickDimensions a lot for marketing automation. It’s a pretty good tool. But today, working with their support, I came across this doozie of a bug. I had a form that was working fine unless an option set for country was on it. Here’s what we found – when you create a web form and map it to an option set, it will replace the substring “options” in the field name with “select”. My option set was called “new_countryoptionset” and ClickDimensions failed because internally it thought the field was called “new_countryselectet”. I recreated the field and called it “new_countrypicklist” and it worked fine. I don’t know whether to laugh or cry. But if you are having issues with option sets in ClickDimensions keep this in mind.

Here’s another old blog I’m republishing. This functionality is now native in CRM 2013 and CRM 2015 as Business rules. Sometimes, you want to one same entity and associate it to two other entity types. For example, you might have a License that could apply to either an Account or a Contact. You could create two entities – an “Account License” and a “Contact License,” or you could use this simple technique to use one entity that appears to be linked to a Contact or an Account. Here’s how: Create your new entity. On the Entity form, add three fields: A “Two Options” field called “Owned By,” and set option 0 to be Account and 1 to be Contact. Set the default to Account (1). A Lookup to a Contact called something like “Owner (Contact)” A Lookup to an Account called something like “Owner (Account)”. Create a new Web Resource with the following code: [code lang=”js”] function licenseOnLoad() { if (Xrm.Page.ui.getFormType() == 1) { ...