By using this website, you agree to our Terms of Use (click here)
If you have run into a situation where you need to change the vendor class for all vendors, you can do this easily with an Import Scenario that imports updated vendor classes from an Excel file. There is just one trick.
Let's say you have an Excel file with two columns: Vendor and Vendor Class that you are importing from.
So you think, "hey, easy, I'll just create an Import Scenario that looks like this":
But then you get the following error when you run it:
Please confirm if you want to update current Vendor settings with the Vendor Class defaults. Original settings will be preserved otherwise.
The reason for this error can be seen when you change the Vendor Class field in the regular Vendors (AP303000) screen. When you change it, this box pops up:
This is why you get an error with the Import Scenario. Since an Import Scenario passes through the same logic as if you were typing the information into the screen, it needs a way to respond to this popup box.
Basically, you just need to add a <Dialog Answer> line to your Import Scenario. The only funny thing is that you have to add the line with your answer before the field that causes the popup to appear. You would think that it should come after, but for some reason it doesn't. Product Developer Evangelist extraordinaire Ruslan explained to me once why, but it didn't make since to me because I'm not a C# developer.
Anyways, just make your Import Scenario look like this and you should be fine (replace ='No' with ='Yes' if you want to respond YES to the popup):
I have a similar need for the customer record. Using the 'Import Customers' scenario to change the class AND for certain records I want to update the payment method. My first attempt in my demo database did not work. And to clarify, I did add the dialog answer to the import scenario, so the records processed and Class was updated however the payment method did not.
I assume it has something to do with the payment methods TAB and the ISDEFAULT checkbox?
in the excel file that downloads from the import scenario I see the following fields:
PaymentMethods->IsDefault
PaymentMethods->PaymentMethod
PaymentMethods->Description
Would any of these need to be updated to complete my scenario?
Your help is appreciated!
Cheers,
K2
@kkeating I'm not sure off the top of my head why you weren't able to do it in one pass, but what about doing it in 2 import scenarios? You could create an Import Scenario that does nothing but update the payment terms.
The Terms field on the FINANCIAL tab of the Customers (AR303000) screen looks like a normal field to me. You should have a field that doesn't have -> after it. When you see -> and then something, it means that it's referencing fields in another object.
@timrodman When I go into the Customer Payment Method screen and I add a record for one of the customers I want to change (manually not via a import by scenario), and add the payment method to that screen for a customer...it does not update the customer record. It simply selects the OVERRIDE check box for that payment method I added on the payment methods tab of the customer.
Maybe I'm missing something regarding the functionality of acumatica...
Yes, customerPM.png is me adding the record to the customer Payment method screen. Picture 2 is the list of all the records that are assigned via the customer payment method screen (in local demo instance).
Picture 3 is the customer record Billing Tab showing the payment method has NOT changed. Picture 4 is the Payment Method TAB showing the online method selected as Override, but not the default.
I changed this customers class with the import scenario....from local to KEY. that should be the only difference from the initial demo data.
Here's my IS from a few years back to update Payment Method. Note that Line Number needs to be inactivated and Cancel needs to be Action: Cancel now (depending on what version you're on). (I couldn't include angle brackets around those words as they get stripped out.)
Also when it comes to debugging issues with Imports, try to replicate exactly what the IS is doing, in the same order of the rows in the IS. Then hopefully you can trigger the issues that the import is having.
@roycelithgo Thank YOu for this, and know that I'm new to Acumatica...is there not a out of the box payment method import scenario?
And for payment method and @@PaymentMethodID, do you use the TEXT based descriptor(PaymentMethodID) or the PMInstanceID?
Also - what is the screen name and provider used for this?
Cheers,
k2
@kkeating No out of box IS for payment methods - hence why I rolled my own.
Screen Name is Customers. Data provider is my own. It's using CSV Provider with only 2 columns needed: Customer ID, Payment Method ID.
Note that you can reverse engineer this by looking at import lines - fieldnames not in square brackets are from the DP.
You should be able to build this yourself - the editor will automatically add the needed lines. Just disable the Line Number line - the rest you can copy from mine.