Hello All,
My question, as the title suggests, is when to setup the user rights for forms, report, etc. Should we setup the user rights before a project starts, or should we do it after all the customizations have been throughly tested and we are ready to deliver it to the customer?
According to me the latter will be more advantageous, as we will have all the customizations in place. So, while running through the user rights setup, the rights will be calculated based on the customizations too (a new table was referred via an insert/update in a particular form, etc.)
What do you all think about this process? This is the MOST tedious process in the whole of NAV. Also, recommendations for tools/process for doing the same will be appreciated.
As a side note, we are using NAV 2009.
Thanks,
Kirtan.
0
Answers
I would have it up before the first training. As the live date approaches, other tasks will pile on. It's always better to get as much done as possible before the live date.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
(Mainly the purpose of User Rights setup is not to allocate certain objects to particular user, but to Block the user to access certain Objects)
1) At the stage of starting of project i.e. before the customization completion, generally client is not ready with the User Accesses. I mean, which user will do what. (In NAV) (If ready then after seeing the system, they can be vary)
2) We will not have all the forms or Reports or codeunits ready to be allocated to the user.
So, after completion of customization, we will agin have to test User Rights and allocate newly allocated objects' user rights.
3) First of all, allocate all the objects to all users. Then after only client will be able to prepare the User Rights template for each user, about which user should be blocked to which objects.
After all, I will suggest we should do the User Rights Setup after completion of all the customization and testing.
Ahmedabad, Gujarat, India
E Mail : ravi.thakkar@hotmail.com
This way the purpose of UAT (in which you play a big role as well) will fail as i never met any client in which client's project manager said make all of them super user even during testing as they want to know how permissions are working, because they know next time after going live, users will say to there PM "Sun of a gun (the way it is said,) i can't see this now, earlier i used to" .
But, at the development time, even developers also are not aware with the objects expected to be used in Coding or any specific object itself.
So, if user rights are setup in advance then also you will have to change them accordingly for new objects and objects used in those objects.
Means again the same task. :whistle:
Ahmedabad, Gujarat, India
E Mail : ravi.thakkar@hotmail.com
:shock:
How can you assign the objects to the user which are not developed yet....
Ahmedabad, Gujarat, India
E Mail : ravi.thakkar@hotmail.com
RIS Plus, LLC
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Kirtan.
The NAV2009 forum is only for NAV2009 technology questions. We changed the definition of the forum some time ago to make it more logical.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Hmmm...
So where do we post questions about Navision versions greater than 5.0 SP1 :-k
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
So in all fairness to kirtangor he did post in what appeared to be the correct forum.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!