I continue to have an error on my Opportunity import that the Contact cannot be empty. HOWEVER, the data in the excel spreadsheet is 100% correct and it appears to me that the import scenario Mapping is also correct. I know 100% factually that the Contact ID in my data is correct. Why am I continuing to see this error message?
+18
Hello,
It seems like the issue might be on the Owner line:
Try using Owner Id where indicated, like this:
Laura
Hi
I set that as you instructed, and verified that in the Excel file there is a valid “Owner” column with valid OwnerID data in it. But still seeing that exact same error. Here is a screenshot of the Import Scenario again.
Thank you,
+12
An important thing to know when building Import Scenarios is that the scenario is essentially performing UI functions, the same as a human would. Knowing this, a great troubleshooting step is to open the screen and perform the functions yourself, exactly as you have them defined.
I believe you’ll find that you cannot use the ‘Open’ action before entering a Subject. Also, unless you’ve customized the Opportunity workflow, OpenFromNew opens a dialog box, which you’ll probably need to provide an answer for, BEFORE the action that causes the dialog.
hi
Note the errors that say that the Acumatica destination field does not exist. What should I be selecting there then?
+12
First off, you seem to be missing the Opportunity ID this go-round.
Have you looked at the existing Import Scenarios for Opportunities? Acumatica often ships some standard that may help you with the basics.
I have to admit, I’m not sure where those values are coming from. I think you just want ‘Contact’ and ‘Owner’ or perhaps ‘Owner -> Employee ID’ depending upon what values are in your spreadsheet.
I did exactly as you suggested. HOWEVER, what keeps happening is that even though I continue to select the “Contact” as the Field/Action Name, when I save the scenario and go back into it, Acumatica keeps flipping my selection BACK to that “ContactID!DisplayName” with that error message/warning. That is what is so frustrating, it is Acumatica that is changing that option in the scenario.
+4
I just tested and was able to successfully import opportunities using the following mapping.
Compare this to your mapping and see if changes are needed.
Ed
Thank you, thank you, thank you
When I manually edited the source field/value to be that =IsNull statement, I WAS able to then successfully import these opportunities.
Thank you very much,
+4
You are welcome!
Glad I could help!
Ed
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
