Skip to main content

NAV 2013 R2 - JET REPORT Configuration with NAV - Part 2

Hi all,

We will start the configuration of Jet Report from the point where we left in Post 1.

we have completed the installation and imported objects into the database.

1 - Open the Role Tailored Client for Windows using the New Service Created in Post1.



2 - Create a web service for Codeunit 14125500 with Service Name as Jet Data Source.
* How to create a web service.



3 - Open Excel, From Jet Menu open Data Source Settings.
Set the Properties as -

Web Service 
Server Name - Your Service Tier Name or IP.
SOAP Service Port - SOAP Port of the service (My case 1047).
Instance - Name of Service (My Case Jet Report).
JET Codeunit - Web Service Name Created in Step 2 (Jet Data Source)
Company - Select The Company Name.


What will happen when your clicks on Drill down of any value in Jet Reports?

In earlier Version it used to open the Classic client of Navision.

From NAV 2013 and later you can specify a different service to open RTC Client for drill down.

You can choose you want web client or Windows Client.

In Data Source Settings Navigate to Drill Down -

a- Select the Drill down method.
b- Specify the path of Role Tailored Client.
c- RTC Server (Service Tier Name / IP).
d- Client service port.
e- RTC Instance.
(Suggested for d & e- Specify the port & instance name that client use to connect instead of new port & instance service created).



If everything is right you will see a Green Icon with Text you are licensed as a....
OR
If there is any issue in configuration you will see a Red Icon with Text You are not licensed for this data source.



If you end up with Red Icon, Just click the URL Text next to ICON and it will show you the issue.



Do post your issues as comments if you face any.

Thanks & Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.