Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Sync Type of New Records Only in Import Scenarios

One of our customers does a daily import of Customers and Vendors from another 3rd party software.  We set up the AP Vendor import scenario with a sync type of "Incremental - New Only" because they regularly export an existing vendor from the 3rd party software regularly.  Our thought was that this setting meant it would only import new vendors.  However, over time, a user noticed a field was getting changed after they imported vendors, and this one vendor was in the source file.  After testing, we found out that the import was the cause of the issue and that it was reimporting the vendor. 

 

After working with Acumatica Support, it was determined that the import is working as designed, and the Incremental - New Only and Incremental - All Records sync types are based off of new versions of the original source file, and not whether or not the record already existed in Acumatica.

 

I am requesting updates to the sync types so that the Incremental - New Only (or a new, additional option) means the scenario will only import new records, and if line is an existing record in Acumatica, i.e. Vendor ID or Customer ID, then that line will get skipped.

  • Chris Love
  • Mar 26 2019
  • Future consideration
  • Attach files
  • Vladimir Panchenko commented
    June 24, 2019 13:39

    Thanks for the feedback. We'll think about adding this mode in the future.

  • Chris Love commented
    March 26, 2019 21:08

    Doug, unless I'm reading this wrong, the @@ construction that you're referencing is still used to update records where you don't know the values of the key field.  In my import, I am creating the key field, so the Vendor ID or Customer ID are "known" in the import.  In this case, I DO NOT want to update the vendor or the customer with my import, I simply want that line/record in the source file to get skipped during the import process if that Vendor ID or Customer ID already exists in Acumatica.  

     

    Example:

    Vendor ID: ABC1234

    Vendor Name: ABC Packaging

    Active Vendor in Acumatica

     

    New Source File (as a new revision or new source file altogether):

    Vendor ID = ABC1234

    Vendor Name = ABC Packaging

    Phone # = 555-555-5555

    Address = 123 Main St

    Vendor ID = DEF5678

    Vendor Name = DEF Beverages

    Phone # = 888-888-8888

    Address = 456 Broad St.

     

    In the situation I am referring to, only Vendor ID DEF5678 would get imported. The import will look at the Vendor ID in my source file and say "Vendor ABC1234 exists in the AP.Vendor table and the rest will get skipped".

    Feel free to reach out to me if you'd like to discuss further:

    clove@asifocus.com

    803-252-6154

  • Douglas Johnson commented
    March 26, 2019 20:37

    Currently there is a function within import scenarios where you can create a custom key using the @@ construction. This looks up a custom key field to see if the record already exists. If it already exists, then it updates the record. Information about how to use this is including in the I100 class in partner university.

  • Karen O'Lane commented
    March 26, 2019 16:04

    This improvement is critical for integration with third-party products. 

  • Brian Kelly commented
    March 26, 2019 14:24

    This seems fairly obvious to me from an integration perspective.  If records already exist in Acumatica, there needs to be a setting to ignore those same records when they appear within a source file for import.  I certainly understand the need to update existing records from an import source file, but skipping those records is just as important.  From a usability and simplicity perspective, giving the user options to "add new records only", "update existing records only" or "add new and update existing records" makes the integration and import scenarios far more powerful and valuable.  You don't want users to edit their source files manually when they are simply trying to bring in records from other systems through an import scenario.  This is time consuming and error-prone.  Someone else must have discovered this before now, right?

  • Cooper Black commented
    March 26, 2019 13:54

    This would be a great feature.