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 Design Studio
Inquire twice issue- AP10.1
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
45
Members:
0
Total:
45
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
User Experience
Lawson Design Studio
Inquire twice issue- AP10.1
Please
login
to post a reply.
0 Replies
0
Subscribed to this topic
13 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
brihyn
Veteran Member
Posts: 95
4/9/2010 1:06 PM
I added a fairly simple script to AP10.1 that upon hitting inquire, using an "Form_OnAfterTransaction", looks at the User Fields tab, and if there's data on the first User Fields field, adds an asterisk to a field on the Main tab.
This thing works great when I log on. I go to ap10, look at a vendor record with data on the user fields, inquire, i get the *. I go to a different vendor record that doesn't have user field data, inquire, * goes away.
I've also tried browsing to a couple random screens, and then back to ap10, and things still work perfect.
The problem is, several users are going to ap10.1, and they have to hit inquire twice on any vendor record to either make the * show up, or to make it disappear if there's no user field data.
So I had them log off, close the browser, and relogon, and of course, things start working for them with a single inquire.
My thought is something from some random screen is getting cached, but I have no idea what. Ideas on why they might be needing to hit inquire twice and why it would go away once they close their browser and re-logon?
I don't know, as I think about it, if now that the user that closed the browser once, will have the problem show up again....
Brian
Please
login
to post a reply.