AugForums.com

An Acumatica User Group

  • Free
    • Start Here
    • In-Person Gatherings
    • Power BI Workshop
    • Podcast
    • Rolodex
    • Blog
    • Forums
  • Paid
    • AugSQL
    • GI Course
    • GI Library
    • Consulting
  • Register
Acumatica Forums

By using this website, you agree to our Terms of Use (click here)

Forums
AUG Forums
Everything Else
Import Scenario to ...
 
Notifications
Clear all

Questions [Solved] Import Scenario to create Change Orders

 
Everything Else
Last Post by NickSM 6 years ago
3 Posts
2 Users
2 Reactions
4,195 Views
RSS
Brian McMillin
Posts: 5
 Brian McMillin
Topic starter
July 6, 2020 10:32 am
(@brianmcmillin)
Active Member
Joined: 6 years ago

I am not able to create Change Orders with an Import Scenario.  Even in the simplest of scenarios, providing only the Project ID and CO Description and saving I am getting successful Prepare, but on import:

Error: X items have not been processed successfully. View name: Document.

Able to do enter through UI with same info with no errors, Reference number of Change Order incrementing and being created on save.

I have to be missing something simple here.  Should Project ID be available as key field?

On 2019 R2 Construction Edition

xChangeOrderTest

 


Topic Tags
Import Scenarios Change Orders Document
2 Replies
Brian McMillin
Posts: 5
 Brian McMillin
Topic starter
July 14, 2020 12:38 pm
(@brianmcmillin)
Active Member
Joined: 6 years ago

Sorry, posted a total novice issued before doing due diligence.  After reading, what should have been read prior to my post, I got if fixed.

Not at all intuitive that you need to feed an invalid or otherwise unmatched value to the key field to generate a new record with an auto numbering sequence.  Also seemingly odd is that value needs to differ for every record imported.  As I did not have that unique key in my data provider, I took a chance with the Now() function to generate my invalid and unique value... and it worked.

Here is screen shot of the working, less than best practice, mapping.  Hopefully this helps somebody else who fails to study the Acumatica University I100 Integration: Integration Scenarios before composing their import scenarios.

Annotation 2020 07 14 131051

Reply
NickSM
Posts: 46
 NickSM
July 14, 2020 8:54 pm
(@nicksm)
Trusted Member
Joined: 6 years ago

Hi Brian,

From my experience I just use the a Sequential Number in the excel file. For example if I'm importing Projects then I set Ref Nbr to ProjectID.

The system knows that the numbering sequence is either Auto Numbering or Manual. If it is Auto Numbering then it uses it, but ignores it. I like your method though as it standardises what to use.


Reply
Tim Rodman and agupta reacted
Forum Jump:
  Previous Topic
Next Topic  
Related Topics
  • Creating a Data Provider with no header row in data
    2 years ago
  • Update PO Lines using import by scenario
    5 years ago
  • Automation Notifications - only sending on CLOSE not HOLD status
    6 years ago
  • Stack Imports
    6 years ago
Topic Tags:  Import Scenarios (4) , Change Orders (2) , Document (1) ,
Forum Information
Recent Posts
Unread Posts
Tags
  • 12 Forums
  • 2,528 Topics
  • 10.9 K Posts
  • 22 Online
  • 2,414 Members
Our newest member: Megan Pawlowski
Latest Post: Credit Reference Report Needed
Forum Icons: Forum contains no unread posts Forum contains unread posts
Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Online Members

 No online members at the moment

Acumatica Forums

Terms of Use & Disclaimers :: Privacy Policy

Copyright © 2026 · AUG Forums, LLC. All rights reserved. This website is not owned, affiliated with, or endorsed by Acumatica, Inc.

‹›×

    ‹›×