Sage 300

 View Only
  • 1.  Customer has an AP import that has been running wi

    Posted 08-12-2013 16:49
      |   view attached
    Customer has an AP import that has been running without incident for years. today it give the following on 1 csv file: Description: Type mismatch, CNTBTCH field should be number. Code: 1042.0.504.1260 Source: 19:45:49 - The batch number isn't in the file, nor is it in any of the other files that work - you create a batch, then import into it. Any ideas?

    Attachment(s)



  • 2.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 16:56
    Phil, even though you create the batch first before you import the file, did the user set the batch number as a value in the import process. We have found it's much easier to require the batch number column and value is required to be in the import file. It can always be 1, but in order to import successfully all fields which have a STAR next to them are required when importing, either in the import file OR you set the value in the import script.


  • 3.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 17:35
    I tried setting the CNTBTCH value in the file, and then I get this: Description: Invalid input. Optional field cannot be blank. Source: 20:30:51 But none of them are! So something else is wrong.


  • 4.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 17:45
    Did you edit the file to be imported? Look at the field it was trying to import? There's probably something out of alignment - an extra field, etc....


  • 5.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 17:46
    I do LOTS of importing like this, so I've hit every possible glitch.


  • 6.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 17:47
    I assumed this is in Sage 300, right? If you want me to take a look at the file, let me know.


  • 7.  RE: Customer has an AP import that has been running wi

    Posted 08-12-2013 17:48
    Figured it out - I really hate inaccurate error messages. The problem was there was an item optional field line (5) BEFORE the actual item line(2).