Navision Attain 3.6 to 4.0 SP1 Executables (Roles/Perm..)

MrWho

Hey!

I needed to upgrade the customers executables from Attain 3.6 to MBS-N 4.0 SP1 to get the ODBC communicate with there .NET Web application.
After doing so I encountered some problems regarding roles and permissions. I thought that wouldn't happen since all the objects are the same, except some obviously.

In the role "All" under permissions I`ve needed to do the following:
1. Added tabledata id 2000000001 "Object" and tabledata id 2000000003 "Member Of" with all the fields set to yes.
2. All with readpermission set to "" expect the ones with ID 0 I set to Yes.

Then mostly of the people at least got logged in, and got the main menu started. But during the day I still had to add some "specific" tables into the role "All", like VAT Posting and so on..

The roles from Navision Attain 3.6 compared with the ones in the restored database in 4.0 Sp1 where 100% match until I started changing it. The restoring hadn't changed it, so WHY was there necessary to do this changes since the "code" or "object" should be just the same?

Please help me understand this?

kine

SQL or Native DB?

jreynolds

I have recently noticed this too. It seems that the 3.60 and 4.00SP1 executables behave somewhat differently with respect to permissions. For example, using the 3.60 executables it is possible to run DELETEALL against a table that you do not have delete permission to, provided that no records are selected for deletion. However, using the 4.00SP1 executables the same process will generate a permission error.

kine

It is because older versions on SQL were using one appication role with all permissions (Navision still can count records etc.), 4.00SP1 is creating role for each user with just as many permissions as set in Navision - it means, you have no permission on the table - Navision is not able to do anything with the table - count records, deleting etc...