planetbluau
Programmer
Environment: Sage 300 2102 PU2 | SQL 2012
I have a installation with 3 companies. Two (Company A and B) are live production db's and one (Company T) a test. Users have a range of User Authorisations in Company A and B. (For the purpose of this post, I will only talk about company A and T. Company T has very liberal User Authorisations to allow testing. When I dump from Company A and load that into Company T, it blows away all User Authorisations that existed in company T. And it also does not carry the ones from Company A, which I presume to be correct. Even though when I open the User Authorisations module, I see all the entires that previously existed in Company T, but to get them to actually work, I need to go through each one and 'refresh' as it were, using the same setting! Why? What am I doing wrong?
Each company has it's own SYS db. (Is that the problem, should I just use one?)
My goal is to setup User Authorisations in company T, then load company A into T and have the same permisions in T as I started with. (I don't want the restrictive permissions of A to carry across.) It this possible? I have not had this behaviour before. (But often I dont use SECURITY on a test db if the (small) client allows users to see all data.)
Sorry for the long-winded explaination, but wanted to give the picture.
Can anyone steer me in the right direction as how to best manage User Authorisations when dumping and loading?
Again, thank you all.
Rod
I have a installation with 3 companies. Two (Company A and B) are live production db's and one (Company T) a test. Users have a range of User Authorisations in Company A and B. (For the purpose of this post, I will only talk about company A and T. Company T has very liberal User Authorisations to allow testing. When I dump from Company A and load that into Company T, it blows away all User Authorisations that existed in company T. And it also does not carry the ones from Company A, which I presume to be correct. Even though when I open the User Authorisations module, I see all the entires that previously existed in Company T, but to get them to actually work, I need to go through each one and 'refresh' as it were, using the same setting! Why? What am I doing wrong?
Each company has it's own SYS db. (Is that the problem, should I just use one?)
My goal is to setup User Authorisations in company T, then load company A into T and have the same permisions in T as I started with. (I don't want the restrictive permissions of A to carry across.) It this possible? I have not had this behaviour before. (But often I dont use SECURITY on a test db if the (small) client allows users to see all data.)
Sorry for the long-winded explaination, but wanted to give the picture.
Can anyone steer me in the right direction as how to best manage User Authorisations when dumping and loading?
Again, thank you all.
Rod