Hi,
I have created field level security to disable Delete button. It's working perfect in test server but not in production. In Production If power user applied FLS to own-self its working but applied for other user no effect. End user window have been modified by VBA too.
Please guide me where i am missing. FLS is registered in Production server .
Thanks & Regards.
Amir Reza.
K.S.A
*This post is locked for comments
The Best thing I could suggest at this point to debug your issue with that particular user is to install the GP Power Tools and run the security profiler when the user attempts to open the form and compare that profiler trace with another user that is working properly... something must be different do cause this issue... The GP Power Tools will certainly be helpful in your case (formerly known as SDT - Support Debugging Tools).
Hi Bucher,
Thanks for your kind support.
1. I crossed check many times there is proper combination of user/company/FLS definition is checked. Same as you mentioned in image.
2. And all the users for whom FLS applied having modified/customized form in GP.
Still i am facing same issue.
Thanks & Regards,
Amir Reza
Hi Amir,
What you describe here definitely tells me that your problem is related to the security... The fact that user A can logon on user B's workstation and have the FLS working properly indicates a missing settings somewhere in the security..
The first thing you need to make sure is that that proper combination user/company/FLS definition is checked :
The second point is to validate if the form you added FLS settings is not a modified / customized form in GP, in which case you need to assign security to that alternate form.
Administration >> Setup >> System >> Alternate/Modified Forms and Reports
If you checked all this, you should be fine..
Hi Bucher,
yes i noticed yesterday it is working only for one user at all but applied for five users.Suppose i applied for A,B,C,D & E users. For A user its working but not for B,C,D & E. Even If user A sign in from user B machine its working for user A.
Please help me to get out of this issue. I don't know where i am missing.
Thanks & regards.
Amir Reza,
Riyadh, K.S.A
Hi Amir,
[...] Today i noticed for one user in production working fine but not for others. [...]
Does that mean it worked for the other users as well until today ? or did you just notice that it was working only for one user at all ?.. previously you mentioned that it was working in TEST only and not in your production environment.. what did you change to make it finally work ?
Hi,
Thanks for your kind response. Yes Dynamics.set file for both having same entries listed in the same order. Today i noticed for one user in production working fine but not for others.
Thanks & Regards.
Amir Reza
K.S.A
Thanks Almas,
Yes i am talking about UPR_Employee_MNT. Irony is that it's working absolutely fine in test environment but not in production. I suppose something missing in production server configuration. Other customization in RM_Batch_Entry, SOP_Entry etc.. also not working in production though it's perfect in test environment. As mentioned above i cross checked many times whether properly applied or not. yes properly applied. Don't know where i am missing.
Thanks & Regards.
Amir Reza.
K.S.A
Are you talking about UPR_Employee_MNT? Are you selecting the correct product which creating field level security, because you can find this window in HRM Solutions and in Microsoft Dynamics GP too.
Hi Amir
In your test environment, do you have exactly the same products in the Dynamics.set launch file in the same order?
FLS uses a trigger when the window opens to disable the field. It is possible that some other product is re-enabling the field.
David Musgrave
Original developer of Field Level Security
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (