You Do Not Have Permission To Modify/Read/Execute/Insert Records in the....

You Do Not Have Permission To Modify/Read/Execute/Insert Records in the....

This is the most common error message that a user will face and also one of the easiest to figure out...with the right know how! 

Examples: 

-You do not have the permission to insert records into...

-You do not have the permission to modify record in the...

-You do not have the permission to execute...

-You do not have the permission to read...

To find out which permissions need to be assigned to a user for a specific error message you can do the following: 

1. Read the error message! - This error message is referring to the 'General Ledger Setup' table and the permission to 'Modify' the records within it. 

2. You must log into the Database as a super user/ or a user with the permission to the object designer.

3. Open the Object Designer via >> Tools >> Object Designer.

4. Select the 'Table' option and use the Find function (Ctrl-F) to search for the 'General Ledger Setup' table -. (or whichever table is causing the issue).

5. As you can see from the above screenshot the table in question is No. '98'.
6. Navigate to the Permission table - this is 2000000005 - (or search for Permission). >> Then run this table (Ctrl-R) or just hit the 'Run' button.
7. Once the Permission table is open you can then filter the 'Object ID' column for the relevant Table ID. In this case '98'. To filter you can use the filter button or press F7.
8. Once this is filtered you will see a list of 'Roles' which relate to the Object in question. As you can see below we are looking for a Role with the modify permission. You would need to select the most appropriate for the user ie. If they worked with Jobs - we would use the 'JOB-JOBS, EDIT' permission.

Note: You can clear all the filters and then for example, filter by the Role ID - 'JOB-JOBS, EDIT' this would give you a clear indication of what other permissions this would give to a user. 

9. Assign the relevant role to the User and then synchronize the logins (see my other post on Synchronizing logins). This should then resolve the issue for the user. 

In another post I will cover how to make your own permissions so you can start tailoring roles to certain users. 

Andy

Internal Error 2 In Module 10.

Internal Error 2 In Module 10

If you receive this error please refer to the following post to fix the issue: 

http://navguides.blogspot.co.uk/2013/06/delete-your-zup.html

Andy

Stuck Filters - "'01/01/' is not a valid date" - Page Data Personalization

Stuck Filters - "'01/01/' is not a valid date" - Page Data Personalization

Sometimes in Nav RTC user will experience issues whereby a filter (which is erroneous) can get stuck and as a result will stop a page from opening.

An example of this is the 'G/L Analysis by Dimensions' page off the Chart of Accounts. A user can enter an incorrect date into this page - and the next time this page is opened (using the previously saved date filter) the page will not be able to open and will throw up an error such as the following:

One way to fix this is to reset the 'Page Data Personalization' for the affected user. 

To fix you can do the following:

1. Open Classic Client

2. Open the Database

3. Tools >> Object Designer

4. Search for the Table named 'Page Data Personalization' >> Run

5. You will now need to find the affected Page (my example is using Page 408) >> And then delete the line for the affected user - in my case DOMAIN\Username. 

Note: To find the page that this issue is affecting you can find a computer where the page opens correctly (presumably another user). >> Ctrl - Alt - F1 or >> Top Right corner >> Question Mark >> About this Page. 

Andy

User Sessions In NAV / Killing Sessions In NAV

User Sessions In NAV / Killing Sessions In NAV

Sometimes we have the need to find out who is logged into Nav. Especially if someone can't log into Nav due to a license issue. A typical example of this is if a user has left for the evening and has kept themselves logged into Nav, as a result one concurrent license session is being used. This can cause issues if the user has a day off the next day - as this will limit the amount of users who can log in. 

To kill / find out which sessions are running in NAV you can do the following:

1.    Open your Classic Client >> Start >> All programs >> Microsoft Dynamics NAV for SQL Server.

2.     File >> Database >> Open (Windows Auth or DB login)

3.      Ctrl – O  - to open your Company (doesn't need to be done - but I like to check I'm logged in successfully.)

4.      File >> Database >> Information >> Sessions >> User Sessions Drill down.

5.  Look for the users who are logged In – highlight the line and use the ‘Delete’ key if you want to kick someone out of Navision. (As we can see below - 2 support sessions are open, and the SupportQueue).

Note: Ignore the SA logins as they will typically be processes that are running on the SQL server, however - if the 'Application Name' is either 'Microsoft Dynamics NAV RTC' or 'Classic Client' then these are actual logged on users. 

 Andy~

Backup and Restore a Database using the SQL Server Management Studio

Backup and Restore a Database using the SQL Server Management Studio

Backing up and Restoring your Database is one of the most important things you can do. Being able to do this quickly without affecting working users is also important - that is why it is recommended that backing up and restoring your database is done from SQL Server Management Studio.

Note: This is a better way to Backup/Restore than using the Navision client as it is quicker, safer and wont lock tables - see my other post (Backup/Restore using Navision Client). 

Backup Database

1. Log onto your SQL Server.
2. Open the SQL Server Management Studio.
3. You should be greeted by a 'Connect' dialogue box - I'm logging in with SA (default SQL Super), you can however use Windows Authentication. Chances are if you are a Super in NAV you can use your Windows Login to Backup/Restore.



4. Expand the 'Databases' folder. I'm going to use the 'Test Database' to try my backup.

5.  Right Click the 'Test Database' >> Tasks >> Backup

6. Choose your Backup location >> I have chosen C:\Data. Also ensure you select 'Disk' as the Backup location. >> Then select 'OK'.

Restore Database

1. Log onto your SQL Server.
2. Open the SQL Server Management Studio.
3. You should be greeted by a 'Connect' dialogue box.



4. Right Click the Database folder>> Restore Database...

 5. Make sure to select source as 'Device' and drill down to find your Backup file.  Now depending if   you want to Overwrite the Existing / or Creating a database you must choose the destination. In this scenario we are making a new database called 'New Database'.

 6. You must also select the 'Restore' tick after finding the file. 

  7. You need to also determine where the Log and Data files will get stored when restoring your DB. As I want to keep the original Database intact (Test Database) I am editing the filepath to give the 'New   Database' a unique name so as not to overwrite the existing.

  8. Press OK and your done. 

  Andy

Saving a View in NAV RTC

Saving a View in NAV RTC

Sometimes we have the need to access 'personalized' data quickly. For example we may want to filter some records and be able to call these up at the moments notice - rather than entering a certain set of filters each and every time we want this info. 

To do this we can use the 'Save View As...' feature of NAV. This will store the filters and save the 'page' into the Role Center for future use. 

Note: This cannot be transferred to other users and will have to be set up for each and every user. 

1. Define the filters you want to save. For this example I am using the Sales Quotes List View and using a filter of 'Assigned User ID' = 'SA' 

2. Select the 'Sales Quotes' drop down box >> 'Select the Save View As...' function.

3. This will then prompt the user to name the new view. I named this 'Sales Quotes - [View]' but it can be called anything. 

4. This can then be accessed from the 'Home' location within the RTC as a pre-set filtered page. 

Andy~

Backup and Restore a Database using the NAV Client (2009 / 2013)

Backup and Restore a Database using the NAV Client (2009 /2013)

One method of Backing up and Restoring a database is using the Navision Classic Client. This however can take longer to do (in terms of processing) and can cause table locking - so is not recommended for working hours. 

Note: The best method of doing a backup is via the SQL Server Management Studio (covered in another post). 

To perform a backup of the database you must do the following: 

1. Open the relevant Database.

2. Tools >> Backup... >> Select the relevant companies (or Entire DB) >>  Always select Objects/ Data common to all companies >> Add a Description >> Choose a location to save >> OK

 To restore a database do the following: 

1. Open the Database (whether it be empty or already populated). 

2. Tools >> Restore... >> Select the relevant backup file  >> OK.