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
Update to HR11 works in LID but not Add-Ins
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:
268
Members:
0
Total:
268
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
Update to HR11 works in LID but not Add-Ins
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Dennis Setliff
New Member
Posts: 3
8/16/2012 9:26 PM
We are still using LAUA/LID. I can directly update the Phone Number on HR11 in our Dev and Prod environments/product lines. I can us Add-Ins to update the Phone Number through HR11 in our Dev environment/product line but I get a "Security violation" return message in our Prod environment/product line. I copied the security class from Dev to Prod thinking there may be a difference in LAUA but still get the same message. Any suggestion on where or how I could track down the "Security violation"?
Thanks
Shane Jones
Veteran Member
Posts: 460
8/17/2012 3:28 AM
There is a hr screen for maintaining field level security but I can't remember the screen. Maybe HR10???...
Shane Jones
Veteran Member
Posts: 460
8/17/2012 3:19 PM
I just looked and the security information I was referring to is on HR09 and HR10 .... (You set a user level security for a field and a user. This "might" be a decent place to look - just to see if they are different between your systems.) I hope this is it but my guess is they will be the same and you will need to keep looking.
Dennis Setliff
New Member
Posts: 3
8/17/2012 4:00 PM
We checked the HR09 and HR10 in Dev and Prod and they are the same. It looks like I am not able to update any field on the HR11 using Add-Ins. I have tried using Add-Ins in Prod to update the Nick Name, Birth City, Email Address, and Phone Number with no luck at all. I can update all the fields using LID and keying into the HR11 screen in Prod and Dev and I can update them using Add-Ins in Dev. But I get a Security violation error message when trying touse Add-Ins to update the fields in Prod. It is like Add-Ins is not looking at LAUA.
Shane Jones
Veteran Member
Posts: 460
8/21/2012 5:23 PM
Sorry if you already checked but do you have add-ins enabled in security administrator for the user account?
Dennis Setliff
New Member
Posts: 3
8/21/2012 6:55 PM
I do have add-ins enabled and can use add-ins to update other forms. I was able to change my security class to a different security class and update HR11. The problem is the security class I was in looks to have the same access to the HR11 as the one I changed to. I would think if the security class prevented updating HR11 using add-ins that it would also prevent me from updating the HR11 data using LID. Does add-ins look at security in some other place outside of LAUA that gets updated through a process that might have failed?
I got past my immediate problem but I am puzzled by add-ins behavior and questioning if I have stumbled on to a symptom of a much larger LAUA problem.
Thanks!
You are not authorized to post a reply.