Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

Can we get sf_refresh to ignore newly created custom fields?

We use DBamp to replicate data overnight to a local server, and then several times per day we run a refresh, this is normally ok - until someone add's a new custom field, when this happens sf_refresh reports an error and stops.

Is there any way we can get it to ignore these changes and just do it's best to refresh the data as we use this data in a quoting application and need to get fast access to new accounts and opportunities?
1 person has
this question
+1
Reply
  • The Stored Procedure Reference chapter of the DBAmp manual documents the many options you can use to control sf_refresh behavior when a schema change occurs.

    In your case, you should read and understand the 'Subset' option.

    The DBAmp doc is available at http://www.forceamp.com/hats/DBAmpDoc...

    Let me know if you have any questions after reviewing the material.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Thanks for the prompt reply,
    Am I correct in thinking that subset will allow you to only download a sub set of columns? so If I refreshed subset AM this would refresh all columns who's first letter begins with a letter falling between A and M? this would work IF all custom fields were created with the first letter of "Z" - so we could refresh A to Y without problem. the Issue with that we don't know the letter first letter of the newly created column.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • You are confusing to different features: the column subset feature and the subset option of the sf_refresh.

    You want to the subset option of the sf_refresh. From the doc:

    The optional parameter SchemaError can also be set to ‘Subset’. If there is a schema change to the salesforce object, sf_refresh will try to determine a valid subset of columns that exist in both the local table and the table on salesforce.com and will refresh the local table based on that column subset. 'Subset' implies that new fields added to the salesforce object will not be captured by the sf_refresh. In addition, deleted fields will still remain in the local table. To alter the local table and immediately delete columns no longer in the salesforce object, set SchemaError to 'SubsetDelete'. To match the schemas back up, either run sf_replicate or sf_refresh with SchemaError of 'Yes'.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • I’m thankful
    Ah! explains my confusion - Subset fixed it thanks for your help
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned