Add-ins error: "New value must be spaces because line has no item"

 1 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages


Kelci











Basic Member



Posts: 11




Basic Member



    I'm hoping someone can assist with this, because I'm stumped!  I'm testing out a mass upload of pay increases in our test environment and encountering an error when I attempt to upload the changes:  "New value must be spaces because line has no item"

    This is a template that I've used successfully in years past, but had to update a handful of the fields after we upgraded Lawson to v9.  The template as it currently exists (after my edits) is:

     

    _f0
    TC
    _f52 PCT-COMPANY
    _f55 PCT-EMPLOYEE
    _f58 PCT-ACTION-CODE
    _f62 PCT_EFFECT_DATE
    _f66 PCT-REASON11
    _f74 IMMEDIATE-ACTION
    _f77 PCT-UPDATE-BENEFIT
    _f79 PCT-UPD-ABS-MGMT
    _f81 PCT-UPDATE-REQ-DED
    _f107:0 PCT-NEW-VALUE-11
    _f347 _HK
    (H),_f9 ORIG-COMPANY
    (H),_f10 ORIG-EMPLOYEE
    (H),_f11

    ORIG-ACTION-CODE

    Any ideas what could be causing this error, and how to resolve?  Input is appreciated!



    Kelci











    Basic Member



    Posts: 11




    Basic Member



      After much research I was able to modify my PA52 upload template to work on v9 - posting this here in case it helps anyone else.  My template now reflects the following:

       (H),_f0,TC

      _f52,PCT-COMPANY

      _f55,PCT-EMPLOYEE

      _f58,PCT-ACTION-CODE

      _f62,PCT-EFFECT-DATE

      (H),_f63,PCT-ACTION-NBR-K  (I added this per KB 1199678)

      _f66, PCT-REASON11

      _f74,IMMEDIATE-ACTION

      _f77,PCT-UPDATE-BENEFIT

      _f79,PCT-UPD-ABS-MGMT

      _f81,PCT-UPDATE-REQ-DED

      (H),_f14,PAT-FLD-NBR-111 (I added this per KB 1204713 - it holds the value "62" which is the Rate of Pay field number)

      _f107:0,PCT-NEW-VALUE-11

      _f350,_HK  (A concatenation of Company - ours is four digits so 5 zeroes added, EE Number, Reason, Date, and Action, Nbr with 3 leading zero's - e.g. 1000000001234PAY CHANGE201607030001)

      (H),_f9,ORIG-COMPANY

      (H),_f10,ORIG-EMPLOYEE

      (H),_f11,ORIG-ACTION-CODE

      (H),_f12,ORIG-EFFECT-DATE

       

      It's always an interesting process when a template that has worked for years suddenly no longer works, but I'm happy to report that it is working beautifully now!