Sage 100

 View Only
  • 1.  Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 10:35
    Help! Installed PU7 for a client that is on v2014. They went from PU3 to PU7. They have a VI Job that imports into WO Trans Entry. Before the Product update, it worked. Now, if a WO is number as 12345.7, the job imports this as 0012345 and does not recognize the .7 - Any ideas? I tried importing the column as a temp field and then calculating the WO # from there but no change.


  • 2.  RE: Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 10:36
    are there any performs on your vi Job ?


  • 3.  RE: Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 10:38
    no


  • 4.  RE: Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 10:58
      |   view attached
    What about using the Sub String function and breaking it up by putting 12345 in the Start 1 length 5 then put "".7"" in start 6 length 2 totally theory but that is what I would shoot for next. I'm guessing the DOT is the problem sage is interpreting that as a record delimiter.


  • 5.  RE: Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 11:00
    Just figured out that Sage is rounding the WO number if there is a decimal place in the field. At a loss for how to prevent this though.


  • 6.  RE: Help! Installed PU7 for a client that is on v2014

    Posted 01-21-2016 14:57
    There is a similar issue importing Job Cost data. Told client to start using an underscore instead of a period. That worked