• arniep
  • NEWBIE
  • 0 Points
  • Member since 2017
  • Business Analyst
  • CC

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 2
    Replies
We use a custom api load (not data loader or data import wizard) to update exisiting contact records with our saas application usage data, for example, logins and user id's.  If the contact record already exsists we want duplication and match rules to prevent a duplicate from being created and we want to use the contact's email address as an exact match.  Do custom API contact imports and updates use duplicate and match rules like data loader and data import wizard? How can we ensure our custom API import can match against the contact's email address?
  • January 05, 2017
  • Like
  • 0
We want to use an account object custom field for an email trigger alert based on the old value of the field.  We ran a report and see the old and new value using the account history report but we are unable to produce the old value for our custom field named 'lifecycle prior value.'  SF support directed us to the forum for help from SF developers.  We appreciate any help!
  • January 05, 2017
  • Like
  • 0
We want to use an account object custom field for an email trigger alert based on the old value of the field.  We ran a report and see the old and new value using the account history report but we are unable to produce the old value for our custom field named 'lifecycle prior value.'  SF support directed us to the forum for help from SF developers.  We appreciate any help!
  • January 05, 2017
  • Like
  • 0