Results 1 to 3 of 3

Thread: Updating with Import without Record Duplication

  1. #1
    Outis is offline Junior Member
    Join Date
    Jan 2009
    Posts
    3

    Default Updating with Import without Record Duplication

    The import utility supports the ability to 1) create new records, and 2) to create and update records. However, there is no stand-alone update option. Related threads indicate that updates without row insertion are possible IF the primary key is supplied at the time of import. If there is no back end access to report on primary keys, is there another front end work around whereby existing records can be updated while eliminating the possibility of record duplication?

    Thank you!
    Outis

  2. #2
    SergeiLo is offline Senior Member
    Join Date
    Dec 2008
    Location
    Minsk
    Posts
    37

    Default Re: Updating with Import without Record Duplication

    Hello Outis,

    Quote Originally Posted by Outis View Post
    The import utility supports the ability to 1) create new records, and 2) to create and update records. However, there is no stand-alone update option. Related threads indicate that updates without row insertion are possible IF the primary key is supplied at the time of import. If there is no back end access to report on primary keys, is there another front end work around whereby existing records can be updated while eliminating the possibility of record duplication?

    Thank you!
    Outis
    What is your source? What do you try to import/update/upsert? Do you have unique fields in your source and SugarCRM target table as well to update your records by?

    Regards,
    Sergei

  3. #3
    Outis is offline Junior Member
    Join Date
    Jan 2009
    Posts
    3

    Default Re: Updating with Import without Record Duplication

    Sergei,

    Thank you for your reply. Since my original posting, I've learned that a true Update is available when a primary key is known. In my example, I wanted to update Accounts with the fact that a given form had been received and filed. By including the primary key (record id) of the Account at the time of Import > Create and Update Records, in my source data, I was able to mass update records without creating duplicate Account rows.

    Thank you again. There'll be some related threads on primary keys and front end reporting that I'll want to log later as well.

    Outis

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 2
    Last Post: 2009-03-14, 08:34 PM
  2. Updating records with import
    By jaymcd0626 in forum Help
    Replies: 6
    Last Post: 2009-03-10, 08:09 PM
  3. Updating Record through SOAP
    By darcy.rippon in forum Developer Help
    Replies: 0
    Last Post: 2008-09-22, 09:03 PM
  4. Project duplication = task duplication
    By regeasy in forum Feature Requests
    Replies: 5
    Last Post: 2007-12-18, 01:48 AM
  5. Replies: 3
    Last Post: 2007-12-06, 10:14 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •