Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Linkhttps://appexchange.salesforce.com/listingDetail?listingId=a0N30000000q5oPEAQ
PricingFrom US$2000/year http://www.prodly.co/pricing/
5 Users / YearFrom US$2000/year
Description

Moves data from Prod to Sandbox or Prod to another Prod

Change Sets for Data - I like that tag line.

...

You have to grant third party access to their Heroku App

Image Modified

Documentation

...

  • Set the UI Setting to enable updates to records with inactive owners before deploying. 
  • Actually - make sure all your records are owned by active users anyway, or you may get this error OP_WITH_INVALID_USER_TYPE_EXCEPTION:Operation not valid for this user type:-- and it looks nasty http://salesforce.stackexchange.com/questions/24390/mysterious-op-with-invalid-user-type-exception-operation-not-valid-for-this-use    
  • Wait a while after you create a sandbox to start deployment or you will get a 503 error. 
  • Change the layout of the Deployment Results page to display Deployment Batch and Deployment Record Results in reverse DateCreated order, so you can refresh and keep an eye on what's going on. 

Issues

Setup

  • It doesn't give you correct error messages until you go to deploy it. 
  • Bug? I have two fields on Campaign named Start Date (yeah, I know, I didn't set it up). The custom fields do not show. is this because it is just reading the metadata based on Label and not duplicating the fields? 
    • Yes! that is exactly what it is. I renamed the standard Start Date and End Date to XStart Date and XEnd Date and now the custom Start and End dates appear. PLEASE display fields based on API Name not Label. 
  • It doesn't seem to like dates with GMT offsets  eg 2015-01-01T00:01:01+10:00 ERROR at Row:1:Column:70 line 1:70 mismatched character '+' expecting set null

...

  • What is Create Missing on External IDs - one was on a custom date field on Campaign - how would it create missing dates? Nothing in the docco about this. 

Deploy

...

WHYYYYYYY? Is this just a one-shot deal - once you do a deployment you can NEVER do another one? It went and DUPLICATED lots of data in my Sandbox when I started the deployment again. WHY!?!?!? This product would be so good if this was not the case? But then could not create many of the related records that did not make it through in the first deployment due to the fatal error - so now I need to either - refresh my whole sandbox and start the deployment again, delete all the newly created records and manually add the ones that were missed, or truncate all objects and start the deployment again. What if it fails the second time around?

If this was more of a "Continual Deployment" tool it would be fabulous.

...

  • Why would it not be able to move users over - error is REQUIRED_FIELD_MISSING:Required fields are missing: [Username, ProfileId]:Username ProfileId - this is a freshly pressed sandbox - can't there be a lookup on something other than UserID? Doesn't Replicate User handle this? 
  • Why am I getting errors like this INVALID_CROSS_REFERENCE_KEY:Record Type ID: this ID value isn't valid for the user: XXXXXXX:RecordTypeId -- when I have set Replicate RecordType?
  • Does it not work with NPSP - this error Ooops looks like there was a problem with the deployment: InvalidBatch : Failed to process query: INVALID_FIELD: CMFL__CustomerPriority__c, OwnerId, RecordTypeId, OwnerId, Contact_Person__c, npe01__One2OneContact__c ^ ERROR at Row:1:Column:698 duplicate field selected: OwnerId
  • Why is this error happening? INACTIVE_OWNER_OR_USER:operation performed with inactive user [XXXXXXZ] as owner of contact:-- and it was happening still after I turned on the new setting to allow for updates to records with inactive owners. 
  • WHY OH WHY Am I getting this error - it started, it did stuff, then it failed with this error? Ooops looks like there was a problem with the deployment: Server returned HTTP response code: 503 for URL:
    • I can understand a freshly-pressed sandbox could give this error if you tried a deploy 5 mins after it was created, like I did, but to start, then get that error? 
  • FAAAAAAAARK! Now I'm getting this error and deployment fails. Ooops looks like there was a problem with the deployment: InvalidBatch : Failed to process query: INVALID_FIELD: Start_Date__c from campaign WHERE ( Start_Date__c IN ('2015-05-30','2016-09-08' ^ ERROR at Row:1:Column:63 value of filter criterion for field 'Start_Date__c' must be of type date and should not be enclosed in quotes
    • Why didn't it pick this up before the deployment started? AND I NEVER set my query to that and Start_Date__c is a valid field AND it previously ran with no issues!!!! WTAF?!?!?!
    • This is my Data Set. It's just making shit up now! So frustrating! 

...