commvault.com commvault.com
Solved

Metallic Salesforce sandbox seeding with wrong Record Type

  • 1 December 2022
  • 2 replies
  • 56 views
R
Rank
Badge

We’re new to using Metallic for Salesforce backups/restores and running into an issue when trying to seed data to a Sandbox: Most of the data is seeded correctly, but records aren’t created with the correct record type.

 

For example, all of our Account records are created with the same record type, even though the source data includes a mix of record types. The same thing occurs with Cases and other custom objects.

 

Does anybody have any tips about how to resolve this? We’ve included the Record Type object in the seeding template but this doesn’t make a difference.

icon

Best answer by Shawn Barker 6 April 2023, 14:07

View original

2 replies

Bryant
Rank
Userlevel 2
Badge +2

Hi RoryT:

I’m looking into this and I hope to find an answer for you.

Rgds,

Bryant

Bryant Bell - Senior Product Manager
S
Rank
Badge

Hi RoryT,

My sincere apologies for the delay in getting back to you, and I hope you were able to find the answer to this in the interim. Salesforce doesn’t support the restore of metadata and it’s the metadata that dictates the record types. It’s required that the metadata in the sandbox is already present and matches the production environment you are seeding from, and then the record types will match.

I’ve included some documentation on the requirements for sandbox seeding below. If you are still experiencing trouble with seeding please reach out to our Tech Support group who will be able to help you sort this out quickly (https://ma.commvault.com/Support).

https://docs.metallic.io/metallic/137228_seeding_salesforce_sandbox.html

  • In Salesforce, create a destination Sandbox that contains the same metadata as your source organization. The Metallic software does not restore metadata as part of a Sandbox restore.
  • Verify that the profile, users (communityNickName), and RecordType are the same on the destination and the source.

Thanks,

Shawn

Reply


Terms & ConditionsCookie settings