Customer Code Modification Prevention
fredlosbanos
Member Posts: 6
Hi All,
Is there a way that we can prevent users from modifying the customer code especially if there are posted transaction for that customer.
Thanks,
Fred
Is there a way that we can prevent users from modifying the customer code especially if there are posted transaction for that customer.
Thanks,
Fred
0
Comments
-
You should handle this through permissions. If you don't want them modifying records don't give them modify permissions for that table.
If they legitimately need to modify records and are renaming them, then they need better training. You get a prompt when you try to rename a record and they shouldn't be clicking Yes on it unless they are really supposed to.0 -
I'm assuming that Customer Code is a custom field in the customer table. I'm guessing you want field level security. You can add a boolean field called Modify Customer Code User Setup table. In the OnValidate trigger of the Customer Code, you can write code along the lines of:
UserSetup.GET(USERID);
UserSetup.TESTFIELD("Modify Customer Code");
Note: You should at least define UserSetup as a local variable to the OnValidate trigger of the Customer Code field in the customer table. This way, only users with a check on the Modify Customer Code in the User Setup table.0 -
Easier said than done. Cause they should be able to edit an address, phone , etc.You should handle this through permissions. If you don't want them modifying records don't give them modify permissions for that table.
\:D/ Perfect world & Perfect UsersYou get a prompt when you try to rename a record and they shouldn't be clicking Yes on it unless they are really supposed to.
How we did it was two little changes.
In the S&R Setup table we added a new field called "Block Rename of Customer No." type boolean.
Added to the S&R Setup form - where permissions decide who can access this form or not.
On The Customer Table...
OnRename()
SalesSetup.GET;
IF SalesSetup."Block Rename of Customer No." THEN
ERROR('You are not allowed to rename Customers');
This allows us to stop changes made in error. But also allows to turn it off if we ever need to.0 -
Savatage wrote:
Easier said than done. Cause they should be able to edit an address, phone , etc.You should handle this through permissions. If you don't want them modifying records don't give them modify permissions for that table.
\:D/ Perfect world & Perfect UsersYou get a prompt when you try to rename a record and they shouldn't be clicking Yes on it unless they are really supposed to.
How we did it was two little changes.
In the S&R Setup table we added a new field called "Block Rename of Customer No." type boolean.
Added to the S&R Setup form - where permissions decide who can access this form or not.
On The Customer Table...
OnRename()
SalesSetup.GET;
IF SalesSetup."Block Rename of Customer No." THEN
ERROR('You are not allowed to rename Customers');
This allows us to stop changes made in error. But also allows to turn it off if we ever need to.
How do you specify which user has permission doing it this way?0 -
you can specify which users have access to the setup tables & forms thru permissions.
or you can not tell them that the checkbox exists in the setup
0 -
Savatage wrote:
Easier said than done. Cause they should be able to edit an address, phone , etc.You should handle this through permissions. If you don't want them modifying records don't give them modify permissions for that table.
\:D/ Perfect world & Perfect UsersYou get a prompt when you try to rename a record and they shouldn't be clicking Yes on it unless they are really supposed to.
How we did it was two little changes.
In the S&R Setup table we added a new field called "Block Rename of Customer No." type boolean.
Added to the S&R Setup form - where permissions decide who can access this form or not.
On The Customer Table...
OnRename()
SalesSetup.GET;
IF SalesSetup."Block Rename of Customer No." THEN
ERROR('You are not allowed to rename Customers');
This allows us to stop changes made in error. But also allows to turn it off if we ever need to.
Thanks all for your replies. I'll try this one then I'll post again what ever will be the outcome..
Thanks again...0 -
fredlosbanos wrote:Savatage wrote:
Easier said than done. Cause they should be able to edit an address, phone , etc.You should handle this through permissions. If you don't want them modifying records don't give them modify permissions for that table.
\:D/ Perfect world & Perfect UsersYou get a prompt when you try to rename a record and they shouldn't be clicking Yes on it unless they are really supposed to.
How we did it was two little changes.
In the S&R Setup table we added a new field called "Block Rename of Customer No." type boolean.
Added to the S&R Setup form - where permissions decide who can access this form or not.
On The Customer Table...
OnRename()
SalesSetup.GET;
IF SalesSetup."Block Rename of Customer No." THEN
ERROR('You are not allowed to rename Customers');
This allows us to stop changes made in error. But also allows to turn it off if we ever need to.
Thanks all for your replies. I'll try this one then I'll post again what ever will be the outcome..
Thanks again...
Hi Savatage, =D>
Your suggestion was successful. We can now control the modifcation of customer code.
Many thanks,
Fred0 -
great to hear. we also did that form item # & vendor code too.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
