Skip to main content
Question

Import Scenario (Contacts): Can Contact ID be auto-generated, and why does a “successful” import not create records?

  • January 28, 2026
  • 3 replies
  • 30 views

Hi everyone,

I’m working in Acumatica 2024 R2 and trying to import new Contacts using an Import Scenario targeting Contacts (CR302000).

I’m hoping to get clarification on two related items.

Question 1 — Contact ID auto-generation

Is it possible to import new Contacts and have Acumatica automatically generate the Contact ID?

Specifically:

  • Should the Contact ID field be:

    • omitted entirely from the Import Scenario?

    • included but left blank in the source file?

    • mapped to <Key: ContactID> in some specific way?

Right now, it’s unclear what the correct “insert-only” pattern is for Contacts when the system should assign the Contact ID.

Question 2 — Import runs successfully, but no Contacts are created

I have an Import Scenario that:

  • runs without errors

  • reports completion

  • does not create any Contact records

No validation errors are shown — the records simply don’t appear in the system.

Notable details:

  • Target screen: Contacts (CR302000)

  • Import intent: insert only

  • Contact ID is currently mapped (though I’m unsure if it should be)

  • Save action is included at the end

  • No errors appear during processing

Despite this, no new contacts are created.

This makes me think I’m missing a required field, key mapping rule, or screen behavior specific to Contacts that isn’t obvious from the Import Scenario UI.

What I’m hoping to understand

  1. What is the correct way to insert new Contacts while letting Acumatica generate Contact IDs?

  2. What commonly causes an Import Scenario to “run successfully” but not actually insert Contact records?

  3. Are there required fields or mappings that must exist for Contacts to be created?

Any guidance or examples would be greatly appreciated — especially if there’s a known working pattern for Contact imports.

Thanks in advance!

3 replies

lauraj46
Captain II
Forum|alt.badge.img+9
  • Captain II
  • January 28, 2026

Hi ​@aifiadam,

Probably what’s happening is that Acumatica is importing the first contact and then updating that record repeatedly instead of creating a new record.  To avoid this I would recommend mapping the ContactID field to a unique value from your data source.  You can either create a column with sequential number on the spreadsheet or use another column that’s unique like the email address.

Hope this helps!

Laura  


  • Author
  • Freshman I
  • January 28, 2026

Thanks, ​@lauraj46! That helps clarify the behavior you’re describing.

One clarification: I am already providing a unique value per row (a sequential number), which is currently mapped to ContactID. With that in place, only one Contact is created, and subsequent rows update that same record — even though Acumatica correctly auto-generates the ContactID for the first insert.

It also appears that the final row of my test data is not processed at all; the single Contact created reflects the data from row #3 in the screenshot.

This is where I’m unclear on the intended pattern: if ContactID is system-generated, why is a unique per-row value still required, and is the correct insert-only approach to leave ContactID completely unmapped?


lauraj46
Captain II
Forum|alt.badge.img+9
  • Captain II
  • January 28, 2026

Hi ​@aifiadam ,

I think your issue is actually on rows 5 and 7 on the scenario where you are looking up the contact record again based on the business account name and then the contact job title.  The arrow means that it is a substitute lookup.  To populate these fields, choose Contact Summary as the target object and you should see those options in the Field or Action column.

Hope this helps!

Laura