Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
User Experience
Lawson Add-Ins for Microsoft Office
Upload Error - new value must be spaces
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
231
Members:
0
Total:
231
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson Add-Ins for Microsoft Office
Upload Error - new value must be spaces
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Amy Sweek
New Member
Posts: 1
7/7/2011 3:01 PM
Trying to change salary class (H instead of S) for employees. My upload is returning an error message stating "new value must be spaces because line has no item". Been doing uploads for a few years and haven't seen this message before. Anyone have guideance on how to proceed?
David Williams
Veteran Member
Posts: 1127
7/12/2011 2:18 PM
I have seen that when you try to add a value to a user field and the user field hasn't been defined (in IC or PO) - does HR have a setup for user fields?
Paul Berkowitz
Basic Member
Posts: 14
7/12/2011 2:33 PM
Yes, in HR04
AngieP
Basic Member
Posts: 11
7/12/2011 2:39 PM
I had this error when trying to upload to PA52 to update a user field thru a personnel action. I had gone thru the process in our TEST environment and then got the error when trying to load in PRODUCTION. It turned out that the action set-up on PA50 in PRODUCTION was different than the action in TEST, so my mapping was off. Once I added the user field to the action on PA50 and ran my add-in again, it worked perfectly with no error. Not sure if you are loading thru PA52, but that is the only place I have expereinced that error. Good luck!
You are not authorized to post a reply.