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.

...

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
Warning

I don't know how I did it but I was doing a final check after setting up a complex setup and I wanted to delete one data set. It deleted EVERYTHING. (This is documented, in the help docs now that I have the help docs, but you will probably do this before you realise how it all works). I bought them all back from the recycle bin but it had lost ALL its configuration. Start again. (sad)

Then It added duplicate data sets, so I tried to replicate what I did by deleting everything, but then I had to go ahead and delete each record one by one. There is

Deploy

  • Grrr! I mass transferred all records to active owners BEFORE I deployed and I am still getting INVALID user errors on some Accounts even though the owner is a current user.

Questions

Setup

  • 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

Warning

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.

Ah, OK. This is what the Upserts are about. Cool. The documentation is very light on the Upserts feature. Yes it explains what each option does, but some real world examples would be really good to have. Again, this is why they need a Wiki and not a PDF document for the help guide.

...