Skip to main content

Salesforce admin gotchas

After coming across some of these for the hundredth time, I've decided to keep a list of bizarre inconsistencies / gotchas in Salesforce.

  • Editable list views for certain objects don't allow editing of record owner field, even though certain object types (e.g. Cases) have a "Change owner" or "Assign" option right there on the list view which does the same thing, so something exactly like this is obviously already implemented.
  • You can mass transfer ownership of accounts, but not contacts. It's because of this.
  • The cli's export-to-csv functionality (force query --format:csv) creates a file that its own CSV parsing functions consider invalid if you try to re-import it (force bulk update whatevs.csv).
  • Adding a custom field to a standard object does not add it to any report types for that object.  But adding a custom field to a custom object does.
  • Unlike every programming, scripting and query language, SOQL doesn't have a comment character.  Not even a single-line one.
  • Rather than updating existing features, Salesforce sometimes makes a completely separate, "enhanced" version of that feature but preserves the old one too (probably for legacy compatibility etc). This would be great if the "enhanced" version was at least at feature parity with the old stuff, but there are plenty of cases where you have to switch back and forth betwen both versions, as certain functionality only exists in the old version and is just never implemented.  In most other SaaS stuff this would be completely insane. Examples below
  • The old "Flows" functionality is pretty nasty but has some useful features (like error handling and iterating) that were never added to the "Process Builder" feature, which tries to be a partial replacement for it but really, really isn't
  • Old profile editor vs "enhanced" profile editor:  the old profile editor allowed you to update settings for multiple objects simultaneously, which is required in certain situations such as the following ridiculous situation from this blog post:
    "... as soon as I went to remove access to the Account Brands object, Salesforce presented an error: I couldn't remove those permissions until I first removed permission from the Scorecard Associations object. Similarly, if I tried to remove permissions from Scorecard Association, I got an error saying I had to first resolve the access permissions on the Account Brands object...You need to revert back to the old Profile Editor, since it allows permission changes to multiple objects before a Save operation is committed"


Popular posts from this blog

Using Log4Net to use both event log and a rolling log file

Here's the config section, note that the applicationNameproperty in the EventLogAppender needs to be the same as the event source in the windows event log that you want to log to.  If the event source doesn't exist, that appender won't work.  In this particular project I create that during install using WiX (which is covered in another post)

    <appendername="RollingLogFileAppender"type="log4net.Appender.RollingFileAppender">      <filevalue="log.txt" />      <datePatternvalue="dd-MM-yyyy" />      <appendToFilevalue="true" />      <locationinfovalue="false" />      <rollingStylevalue="Size" />      <maximumFileSizevalue="1MB" />      <maxSizeRollBackupsvalue="10" />      <staticLogFileNamevalue="true" />      <layouttype="log4net.Layout.PatternLayout">        <conv…

Using WiX to create an event source during install of a .NET framework project

Edit: so I guess I wasn't the only one confused with this stuff, as it's been my most popular post by far!  If I've helped you out or saved you some time, please let me know in the comments :)

In order for this to work, you have to add references to WixUtilExtension and WixNetFxExtension to your WiX project.  Once that's done, add this inside a <Component> element:

<Util:EventSourcexmlns:Util=""Name="EVENTSOURCEGOESHERE"Log="Application"EventMessageFile="[NETFRAMEWORK40FULLINSTALLROOTDIR]EventLogMessages.dll" />
Obviously replace EVENTSOURCEGOESHERE with your event source name.  NETFRAMEWORK40FULLINSTALLROOTDIR is a property set by the WixNetFxExtension which stores the path to the .NET framework v4 directory, but you can replace this with the corresponding property for the directory containing the relevant EventLogMessages.dll file.  So if you're using the .NET framewo…

How to make yourself a Dynamics CRM 2011 Deployment Administrator

Today I needed to deactivate one of our Dynamics organisations, but when I opened the Dynamics Deployment Manager, I received the following error:

"Only the Deployment Administrators are able to use Deployment Manager. You are not a Deployment Administrator."
Bummer. I did a bit of Googling and found this post by Ronald Lemmen (thanks for pointing me in the right direction!).  Since the Dynamics Deployment Manager is obviously checking the MSCRM_CONFIG database for this information I attached a database trace to it and found that it's executing these queries (among many others):

exec sp_executesql N'SELECT  Id, [DefaultOrganizationId], [IsDisabled], [Name]   FROM [SystemUser]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar(41)',@Name0=N'{My windows domain account}'
exec sp_executesql N'SELECT  Id, [Name], [UniqueifierId]   FROM [SecurityRole]   WHERE ((([Name] = @Name0)) ) AND (IsDeleted = 0) ', N'@Name0 nvarchar…