Skip to main content

DIY Salesforce partial copy sandbox using SandboxBerry

Salesforce partial copy sandboxes are expensive, but it's possible to approximate one if you're willing to spend a little time moving the data around yourself with a fantastic little tool called SandboxBerry, which you can get from here. Big thanks to Ian Finch for all his work on it!

Below are the steps I had to go through to get all my data imported. Please let me know if you have any suggestions that could make this easier or more effective!

  1. Make a new development sandbox and log into it
  2. Delete all outbound messages and workflows that relate to integrations with external systems
  3. Save a copy of /ExampleInstructionFiles/ExampleInstructionFile.xml, henceforth called InstructionFile.xml
  4. Decide which object types you want to migrate and add them as SbbObjects in InstructionFile.xml
  5. Deactivate validation rules, mandatory fields and lookup filters for those objects (TODO: write a script to do this by exporting metadata, disabling them all programmatically, then re-importing the updated metadata).  For future reference we had to:
    • Deactivate validation rules on the following: Account, Contact, Charge, Product
    • Remove lookup filters on: Account.Business_Consultant, Charge.Base_Product, Charge.Contact, Charge.Account
    • Make the following fields no longer required: Charge.Account, Charge.Contact
    • Remove the restriction from picklist values for Charge.Billing_year
    • Deactivate the following in process builder: "Set fields on contact and parent account after lead conversion"
  6. If you're using person accounts like we are (ugh), you'll need to exclude the __pc fields as well as "MiddleName" and "Suffix". In InstructionFile.xml, add an SbbFieldOptions section with an SbbFieldOption for each field as instructed in the wiki
  7. Run Sandboxberry, put in your details and click Start!

In general, I'd suggest doing a test run first on just a few records for each object, filtering by IDs like:
Account.where =  Id\= '001900000123456'
Object_Name__c.where = Account\= '001900000123456'
Then run the import and ensure everything shows up as expected for that account.


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…