Sage 100

I am using VI to import customer numbers into the Delete and Change utility in AR. Client is on MAS 200 V2015 SQL. On import, the starting customer number and ending customer number (same customer number in my case) imports fine. The MERGE TO customer number does not import. I get the files imported with bad records. The VI job tells me that the customer number already exists - as if I am trying to set up a new customer number when I am trying to merge to existing customers. Anybody have any insight on how I am messing this up? TIA

Fortunately it's SQL - populate the table directly and skip the VI bugs.

@PhilMcIntosh that is an excellent point. I may try it that way

I don't think you're doing anything wrong. I just did this for a customer for ProvidX version and it worked exactly as you described.

Do your customer numbers need leading zero's?

@RandyMarion, we do not have leading zeros on the customer numbers. They are alphanumeric

Not sure if this applies to you, but back in the day with pre-Framework A/R, the programming was expecting only Renumber entries or only Merge entries. You couldn't mix the 2 in the same import job otherwise errors would occur when it would process.

Thanks @AlnoorCassim . So I know it is not just me....

@CooperBlack - did you get anywhere else with this? I am renumbering customers and the same thing is happening to me. The file is a combination of merging into an existing customer number and merging into a new customer number. I tried separating the file based on what @AlnoorCassim mentioned but the import job still fails on the MERGE TO field. Client is on 2014 Standard so I don't have the option of populating directly in SQL. Its 500 entries....

@KelseyLeerkes - and mine is on 4.5 and all customers are merges, not renumbers, and still no love. Did you get a resolution?

Sorry @KelseyLeerkes and @BethBowers but I got nowhere on this. Luckily I had SQL.