Sage 100

 View Only

  • 1.  Anyone seen this issue with a VI import into Transaction JE?

    Posted 06-07-2024 14:32

    Version 2022.5.  Wondering if it's a bug. The JE actually imports fine, but the Job Log displays a wonky message.VI seems to be looking at the first account beginning with the main account #, which is inactive, even though a different account sharing the main account is the account in the source file. Has anyone seen this before?



    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    ------------------------------


  • 2.  RE: Anyone seen this issue with a VI import into Transaction JE?

    Posted 06-07-2024 14:39

    Skip Source Data Truncation enabled (on tab 1)?  It could be that VI is not seeing the "7" (because account key is 9 digits...).

    If that isn't it, do you have a field in your import job mapped to import that column value?  The error might be related to the Format settings for that source journal.



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: Anyone seen this issue with a VI import into Transaction JE?

    Posted 06-07-2024 14:47

    That was it, @Kevin Moyes. Checking the Skip Data Truncation box did the trick.  Thank you!



    ------------------------------
    Barbara Goldstein
    Sr. Consultant
    DSD Business Systems
    ------------------------------

    Original Message


Related Content