Advertisements

Cumulative Update 04 for Microsoft Dynamics NAV 2017 (Build 15601) – Released in March 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2017, including hotfixes and regulatory features that were released in previous cumulative updates.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2017, see released cumulative updates for Microsoft Dynamics NAV 2017 . Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2017.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2017 cumulative update

See How to install a Microsoft Dynamics NAV 2017 cumulative update .

Prerequisites

You must have Microsoft Dynamics NAV 2017 installed to apply this hotfix.

Advertisements

Cumulative Update 17 for Microsoft Dynamics NAV 2016 (Build 48067) – Released in March 2017

This article applies to Microsoft Dynamics NAV 2016 for all countries and all language locales.

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2016, including hotfixes and regulatory features that were released in previous cumulative updates.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

Note Implementing this cumulative update will require a database upgrade.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2016, see released cumulative updates for Microsoft Dynamics NAV 2016 . Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2016.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2016 cumulative update

See How to install a Microsoft Dynamics NAV 2016 cumulative update .

Prerequisites

You must have Microsoft Dynamics NAV 2016 installed to apply this hotfix.

Cumulative Update 29 for Microsoft Dynamics NAV 2015 (Build 48062) – Released in March 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015, including hotfixes and regulatory features that were released in previous cumulative updates.

Note You must convert the database if you are upgrading to this cumulative update from a cumulative update earlier than cumulative update 9 (build 41779). For more information, see Converting a Database in Help for Microsoft Dynamics NAV.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2015, see released cumulative updates for Microsoft Dynamics NAV 2015 . Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2015.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2015 cumulative update

See How to install a Microsoft Dynamics NAV 2015 Cumulative Update .

Prerequisites

You must have Microsoft Dynamics NAV 2015 installed to apply this hotfix.

Cumulative Update 48 for Microsoft Dynamics NAV 2013 (Build 48066) – Released in March 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013, including hotfixes and regulatory features that were released in previous cumulative updates.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2013, see released cumulative updates for Microsoft Dynamics NAV 2013 . For a complete list of all hotfixes released in cumulative updates for Microsoft Dynamics NAV 2013, view the following CustomerSource and PartnerSource pages:

CustomerSource
PartnerSource

Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2013.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2013 cumulative update

See how to install a Microsoft Dynamics NAV 2013 cumulative update .

Prerequisites

You must have Microsoft Dynamics NAV 2013 installed to apply this hotfix.

 

How to Add my Custom Language Pack to W1 Version?

Post you build the PartnerTranslation solution from inside Visual Studio, choose Build Solution from the Build menu.

This will pick up all translated artifacts, and create three installer files (.msi):

  • Server.msi – Located in the Server\Bin\Debug folder.
  • RTC.msi – Located in the RTC\Bin\Debug folder.
  • WebClient.msi – Located in the WebClient\Bin\Debug folder.

You can check my earlier post for more details:

How do I translate my ResX Files?

Managing Multilanguage support in Navision Overview

 

ilm-01

Install the new language pack on the target computer with W1. To do this, select and click each of the three .msi files listed below, one after the other. The order is not significant:

  • Server\Bin\Debug\Server.msi
  • RTC\Bin\Debug\RTC.msi
  • WebClient\Bin\Debug\WebClient.msi

Each installer quickly shows a dialog, which disappears when the installer has completed.

ilm-02

The language pack is now installed, but you must make some final configuration.

Next step is to register root assemblies with strong name key token in the Add-ins table

Microsoft Dynamics NAV cannot load untrusted assemblies. To enable your custom resource assemblies as trusted, you must register the strong name key in the database:

  1. Open the Microsoft Dynamics NAV Development Environment.
  2. On the View menu, choose Object Designer, and then choose Table.
  3. Navigate to the Add-in table, table 2000000069, and then choose Run.
  4. For each assembly, enter the name and the public key token used when signing the files. The assemblies to add can be found in the Output folder of Partner Translation Tool Project.

ilm-03

To find the public key token, use the Strong Name tool (sn.exe) with the -T parameter.

At the command prompt, enter the following command: sn.exe –T

For example, enter the following command to find the public key token for the Microsoft.Dynamics.Framework.UI.dll file:

sn.exe –T Microsoft.Dynamics.Framework.UI.dll.

The sample assemblies that are included in the Partner Translation solution have the following signature: 15e5b2499d4875c1.

Optionally, you can use PowerShell to register a strong name key for the custom resource assemblies.

New-NAVAddIn -AddInName -PublicKeyToken -Category LanguageResource

Next step is, you need to update the Languages page:

  1. In the Object Designer, choose Pages.
  2. Navigate to the Languages page, page 9, and then choose Run.
  3. Add the Arabic Jordan (ARJ) language to it.

ilm-04

Restart the Microsoft Dynamics NAV Server service

To enable the newly added language, you must restart the Microsoft Dynamics NAV Server service:

  1. Choose the Start button, point to Administrative Tools, and then choose Services.
  2. In the Services window, right-click Microsoft Dynamics NAV Server, and on the shortcut menu, choose Restart.

Connect to the Microsoft Dynamics NAV Server and select the new language

After you have restarted the Microsoft Dynamics NAV Server service, you can then open the Microsoft Dynamics NAV Client and select the new language:

  1. Choose the Start button, and then choose Microsoft Dynamics NAV.
  2. Choose Microsoft Dynamics NAV, and then choose Select Language.
  3. In the Language Selection field, select the new language, Arabic (Jordan), and then choose the OK button.

ilm-05

Complete Captions are not translated for this project yet at the time of writing of this post and it is in progress, but the sample screen will look like one shown below.

ilm-06

Will come up with more details in my upcoming posts, till then keep exploring and learning.

Translating Multilanguage Files in Navision 2017 for Arabic Jordan

Captions and other user interface text that you define for objects in the Microsoft Dynamics NAV Development Environment can be exported to a text file. You can then add new translations to the text file and import the new translations in the development environment. You can add translations manually using Notepad, Microsoft Excel, and so on.

The exported text files contain an entry for each translatable user interface element for the objects that you selected in the development environment. However, the text file also includes entries that cannot be translated. For example, if you export the strings for table 18, the resulting text file contains hundreds of entries, of which fewer than 170 can be translated. The translatable strings include the captions of for all fields and the error messages that you have defined. The non-translatable strings include names of variables, and so on.

In CRONUS International Ltd. demonstration database, all objects are multilanguage enabled, and they include strings with captions in the 1033 locale, English (US). The locale is specified by a multilanguage property such as P8629, but the ID of the actual property is different for different types of strings. However, the locale for the multilanguage property value always starts with the character A. For example, the English (US) captions are identified by the A1033 locale value for the relevant multilanguage property. You can identify which strings can be translated by opening the file in Microsoft Excel and then filter by the English locale.

If you export strings for objects of different types, the text file lists the strings by object type and then by object ID. For example, if you export strings for table 18, page 21, and report 111, the text file lists strings in the following order:

  1. Table 18
  2. Report 111
  3. Page 21

The format of the exported text files can be difficult to read, because for each type of object, the text file contains different types of strings. Each type of string is identified by a property that starts with the character P followed by an ID.

For example, for a table object and the fields on the table, the multilanguage property has the ID 8629.

For option values for fields on tables, the multilanguage property has the ID 8632.

This means that you can identify the type of string when you translate the strings. However, you should filter out all strings that are not translatable, which makes the remaining strings easier to understand.

The following table illustrates the translatable strings for table 18 in the CRONUS International Ltd. demonstration database.

String Description
T18-P8629-A1033-L999:Customer The caption of the table object.
T18-F1-P8629-A1033-L999:No. The caption of field 1.
T18-F7601-P8629-A1033-L999:Copy Sell-to Addr. to Qte From T18-F7601-P8632-A1033-L999:Company,Person The caption of field 7601 and the captions of the option values for the field.
T18-Q1001-P26171-A1033-L999:Do you wish to create a contact for %1 %2? A text constant that defines user interface text.

For more information, see How to: Add Translated Strings By Importing and Exporting Multilanguage Files.

 

tmf-01

Here it is assumed that the Language Module Installer are prepared by translating resx files and Partner Translation Tool project is build and same is Installed.

You can check my earlier post for more details:

How do I translate my ResX Files?

Managing Multilanguage support in Navision Overview

tmf-02

After preparing Language Module Installer and installing the same our next step is to add the translated Captions to CaptionML.

You have other methods to do the same below is one which I have used to get my task done.

Export the objects in txt format from the database (ObjectToTranslate.txt).

tmf-03

My objects have ENU and want to add translation for ARJ.

You can use below PS Script to extract Language Layer from the objects.

Export-NavApplicationObjectLanguage -Source ObjectToTranslate.txt -LanguageId ENU, ARJ -Destination translated.txt

In our objects, we have ENU and we are supposed to add ARJ Caption translation.

Above command will extract the ENU Captions and add entries for ARJ where we can add our translated string for Arabic Jordan.

Open the translated.txt in notepad and save as translatedNew01.txt, make sure you select Encoding = UTF-8.

Open the File [translatedNew01.txt] in Excel as below defined step:

 

tmf-04tmf-05tmf-06tmf-07tmf-08

Translate to Arabic Jordan as one shown in above screen.

Add you translation after [ : ]

Once all done Save your file as shown below:

tmf-09

Open the file in Notepad to check format is not disturbed and output is as below:

tmf-10

Next step in upcoming post.

Till then keep exploring and learning.

 

 

Cumulative Update 15 for Microsoft Dynamics NAV 2016 (Build 47671) Released in Jan 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2016, including hotfixes and regulatory features that were released in previous cumulative updates.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

Note Implementing this cumulative update will require a database upgrade.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2016, see released cumulative updates for Microsoft Dynamics NAV 2016  (https://support.microsoft.com/kb/3108728/ ) . Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2016.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2016 cumulative update

See How to install a Microsoft Dynamics NAV 2016 cumulative update  (https://support.microsoft.com/kb/3109325/ ) .

Prerequisites

You must have Microsoft Dynamics NAV 2016 installed to apply this hotfix.

Cumulative Update 27 for Microsoft Dynamics NAV 2015 (Build 47665) Released in Jan 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015, including hotfixes and regulatory features that were released in previous cumulative updates.

Note You must convert the database if you are upgrading to this cumulative update from a cumulative update earlier than cumulative update 9 (build 41779). For more information, see Converting a Database (https://msdn.microsoft.com/en-us/library/dn271650(v=nav.80).aspx) in Help for Microsoft Dynamics NAV.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2015, see released cumulative updates for Microsoft Dynamics NAV 2015  (https://support.microsoft.com/kb/3014609/ ) . Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2015.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2015 cumulative update

See How to install a Microsoft Dynamics NAV 2015 Cumulative Update  (https://support.microsoft.com/kb/3021418/ ) .

Prerequisites

You must have Microsoft Dynamics NAV 2015 installed to apply this hotfix.

Cumulative Update 39 for Microsoft Dynamics NAV 2013 R2 (Build 47662) Released in Jan 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2, including hotfixes and regulatory features that were released in previous cumulative updates.

This Cumulative Update replaces previously released cumulative updates. You should always install the latest cumulative update.

Note Implementing this cumulative update will require a database upgrade.

Licenses versioning

Microsoft Dynamics NAV 2013 R2 cumulative updates and license key versioning:

  • Microsoft Dynamics NAV 2013 R2 license keys are backward compatible with Microsoft Dynamics NAV 2013 instances.
  • Microsoft Dynamics NAV 2013 license keys may not be used with Microsoft Dynamics NAV 2013 R2 instances. Microsoft Dynamics NAV 2013 license keys will not work with Microsoft Dynamics NAV 2013 R2 CU10 (or later) instances.
  • Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 license keys are not forward compatible with Microsoft Dynamics NAV 2015 instances.

More details is made available in the October 2014 release of the Microsoft Dynamics Perpetual Licensing Guide.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2013 R2, see released cumulative updates for Microsoft Dynamics NAV 2013 R2  (https://support.microsoft.com/kb/2914930/ ) . For a complete list of all hotfixes released in cumulative updates for Microsoft Dynamics NAV 2013 R2, view the following CustomerSource and PartnerSource pages:

CustomerSource
PartnerSource

Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2013 R2.

OData Filtering

If your solution uses OData web services with a combination of filters on $orderBy desc and $top, this results in errors in Dynamics NAV 2015 Cumulative Update 13. To avoid this error, add the following entry to the CustomSettings.config file for the Dynamics NAV Server instance:

<add key=”EnableODataStrictFiltering” value=”false”/>

This disables support for complex filters.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

How to install a Microsoft Dynamics NAV 2013 R2 cumulative update

See how to install a Microsoft Dynamics NAV 2013 cumulative update  (https://support.microsoft.com/kb/2834770/ ) .

Prerequisites

You must have Microsoft Dynamics NAV 2013 R2 installed to apply this hotfix.

 

 

Cumulative Update 46 for Microsoft Dynamics NAV 2013 (Build 47667) Released in Jan 2017

This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013, including hotfixes and regulatory features that were released in previous cumulative updates.

This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.

It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).

For a list of cumulative updates released for Microsoft Dynamics NAV 2013, see released cumulative updates for Microsoft Dynamics NAV 2013  (https://support.microsoft.com/kb/2842257/ ) . For a complete list of all hotfixes released in cumulative updates for Microsoft Dynamics NAV 2013, view the following CustomerSource and PartnerSource pages:

CustomerSource
PartnerSource

Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2013.

How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

 

How to install a Microsoft Dynamics NAV 2013 cumulative update

See how to install a Microsoft Dynamics NAV 2013 cumulative update  (https://support.microsoft.com/kb/2834770/ ) .

Prerequisites

You must have Microsoft Dynamics NAV 2013 installed to apply this hotfix.

For more details check : https://mbs2.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;3216196

 

 

 

Microsoft Dynamics NAV ‘Tenerife’ Developer Preview

As everyone is aware by now that Preview of Development Tools for Dynamics NAV have been released. Going forward which can be used to build extensions and apps in and for Dynamics NAV.

This tool introduces two flavors which you can try out in preview available on cloud.

[A] Make an extension in the client itself. Business consultants and UX designers will love using this drag-and-drop interface. Rearrange fields, rename groups, and reposition elements to build a perfect extension to support an industry-specific solution or implement a business process optimization.

[B] Use the AL Extension for NAV in Visual Studio Code to build powerful extensions based on tables, pages, and codeunits using the new objects: Page Extensions and Table Extensions. Follow this route to build rich extensions that reuse and extend core business logic in your application.

For more details you can refer to the article published by Dynamics NAV Team Announcing the Preview of Development Tools for Dynamics NAV

You can get a free 30-day trial from https://azure.microsoft.com/free/ that will give you access to everything you need.

Secondly, head over to http://aka.ms/navdeveloperpreview. Login to your Azure Subscription. Select your subscription, resource group, location, name, and a VM Admin Password. Leave the remaining fields as their defaults. Accept the terms, Pin to dashboard and select Purchase. The instance takes about 5 minutes to set up, and the VM will be ready about 15 minutes after Azure says Deployment Succeeded.

You need to follow on screen instructions to get everything setup using above 2 links provided.

I am not going to repeat the steps as you can find them via other blogs or follow the steps as you proceed via using above two links.

Few of my readers were complaining about they don’t have access to Azure Subscription or they have already used up the limit now what to do?

Same situation was with me too, but however I managed to get one and done bit RND, if this can be setup on my PC so that I can give it a try or others can use same steps to get it configured, and give it a try.

However I got succeeded in doing so, now I can do the same in my environment.

The Steps I am going to explain below is not the straight forward, and require bit tricks, as required components are yet not released from Microsoft, may we can get in CU-2,  I guess or later when Microsoft is OK to release this feature for everyone.

This action will require several pre-requisite to be fulfilled:

  1. Visual Studio Code (To be Installed)
  2. Dynamics Navision Version (10.0.14540)
  3. Some Modification to web.config to enable designer in Web Client

 

STEP-1

You can download the Visual Studio Code from this link: Click Here

Once file is downloaded install the Visual Studio Code by running VSCodeSetup-1.8.1.exe

And follow the on screen instructions to complete the setup.

 

td-01td-02td-03td-04td-05td-06td-07td-08td-09

STEP-2

Dynamics Navision Version

Make sure you have correct version of Dynamics Navision (10.0.14540)

td-10

Else you will not get this option in your Service Window

td-11

STEP-3

Modification to web.config

You will need to make necessary settings to web.config file to enable designer in Web Client, this file is located at C:\inetpub\wwwroot\DynamicsNAV100 location where your Web Client is installed.

td-12

td-13

 

Now you should be ok to use this feature in your environment.

Once things are setup correct you will be able to find the Client Designer Button on right top corner of the Client Window/Browser.

I will come up with more details in my up-coming posts till then keep exploring and learning.

 

 

 

Configuring Single Sign-On using Office 365 on Navision 2016

Today we will see how we can enable Single Sign-On using Office 365 for Navision 2016.

Before we start we should have Virtual Machine ready on Azure with Navision 2016 installed, Certificates and Nav User is configured. Endpoints are open so that web client can be used from outside Virtual Machine on internet.

It should be hosted on Public IP, then only we will be able to configure it.

For details regarding Azure Subscription you can see my earlier post here.

For details regarding Creating Virtual Machines you can see my earlier post here.

You also need Office 365 Subscription ready for use and you can use the AD of same to configure your Single Sign-On.

Let us start with Admin console of office 365. Click on Azure AD this will create Management Console to work with AD.

SingleSignOn-1

Enter your details and click on Next.

SingleSignOn-2

Enter your details and click on Next, Finally Sign Up.

SingleSignOn-3

It will take few minutes to configure and make it available for you.

SingleSignOn-4

Once your Subscription is ready click on Start Managing my Service.

SingleSignOn-5

From Management Console click on Virtual Machine, if you dont have already to create one for you.

SingleSignOn-6

Select the Virtual Machine in Search for Microsoft Dynamics Nav 2016.

SingleSignOn-7

Select the approprite Virtual Machine from the List.

SingleSignOn-8

Enter your details and Create. For more details see the link provided on top of the post.

SingleSignOn-9

Let us return to our AD, Click on Applications. This will List all you Apps currently available with your AD or office 365.

SingleSignOn-10

Click on Add to configure your Application.

Give a Name and Select Web Application/or Web API, as we are configuring for Web Client today. Click on Next.

SingleSignOn-11

Enter your Web Client URL and Office portal AD URL.  Click on OK.

SingleSignOn-12

Your New application gets registered with your AD.

Select the created Application and Click on View Endpoints.

SingleSignOn-13

Copy the Federation MetaData URL and keep it handy at safe place we will require this in our next step. Close the window we are not performing any changes here.

SingleSignOn-14

Open your Navision User Card.In Office 365 Authentication enter your Office portal user email id which you will be using for Single Sign-On.

SingleSignOn-15

Open your Navision Service Instance configuration and enter Federal MetaData URL which we copied in our previous step.

SingleSignOn-16

Restart you NAV Service.

SingleSignOn-17

Open the Web Client Folder under your IIS. Edit your Web.config file using prefered Editor.

SingleSignOn-18

Enter you Client Service Credentials as AccessControlService.

SingleSignOn-19

Change value of ACS URI as below. You have full explaination of same in the file itself.

SingleSignOn-20

Thats all, Now you open your web client and you will be redirected to Office 365 Login Page, enter your valid office 365 e-mail user id and password you will be authenticated and Web Client is opened.

Thats all for today, I will come up with moredetails in my upcoming posts.

Till then keep exploring and learning.

 

Jet Professional 2017 – Introduction and Installation

Why to switch to and What’s New in Jet Professional 2017?

Its valid question same came to my mind also when i heard about new Release.

Then i tried to explore a bit about it and got an information about some exciting features introduced with it. I will discuss as i progress with my evaluation and exploration with these features.

Here i am giving bit overview about some features and limit to Installation topic in this post. If you wish to know more you will have to wait for my next few upcomming posts.

As per Jet Report Sources:

Jet Professional 2017 makes sharing your reports easier than ever before!  

Reporting with (and without) the Jet add-in for Excel

The Jet Web Portal is an online interface that provides an easy-to-manage repository for your organization’s reports.

Using the web interface and Office 365 Online, you can allow any of your network users – whether they have Excel and the Jet add-in installed or not – to view reports directly from their web browser.

Jet Mobile for Jet Enterprise

Jet Professional integrates with the Jet Mobile web client – allowing you to log into one site to see and run all your reports – and to see all of your business intelligence dashboards.

And… Jet Mobile for Jet Enterprise includes many new features – making your dashboards more powerful and even easier to use.

What’s New?

Publishing to the Jet Web Portal

The Jet ribbon within Excel includes the ability to publish your reports to the Jet Web Portal.  The Jet Web Portal provides a manageable repository for your organization’s reports. All your users – whether they have Excel and Jet Professional installed or not – can run and view reports directly from their web browser.

What is Jet Web Portal

Jet Professional 2017 represents a new way to manage, run and view your business reports. Designed for today’s always-connected, always-moving workforce, Jet Professional 2016 introduces a new Information Management System that allows business users access to their business reports using virtually any device through a simple web interface.

As a user, you don’t need to install anything to run and view reports. Within the Jet Web Portal, you can quickly find the report that you’re after, specify report parameters, run the report to get up-to-the-minute data and view it in Excel Online.

With features like sharing, search, version control and report permissions, Jet Professional 2017 is a complete report management system.

Will comeup with more detailed about new features in my upcomming posts.

Let us move to Installation part.

To get the installation file go to this link : https://www.jetreports.com/support/product-downloads/

After downloading you will get the Jet Professional Installation Files.Zip, extract it.

Install-1

Befor you start installation make sure no Excel instance is running on your system.

I am doing simple one system Instalation, will come up with more details and other options later.

Double click to Setup file to begin with installation.

Install-2

If you have Activation code enter it or you can continue and activate later.

Install-3

Select instalation type as desired, i am installing All Components.

Install-4

Select the features you want to install, since i am performing complete install, so i am accepting all as suggested by default.

Install-5

Select the Account to run the service, and don’t forget to select Add rules to Windows Firewall. Rest all as default suggested.

Install-6

Select the SQL Instance for Jet Service Database and login method.

Install-7

Select desired ports and host detail or accept as suggested as default.

Install-8

Enter Jet Service Tier details or accept suggested as default.

Now your pre-configuration part is completed. Click on Install to proceed with Jet Components Instalation.

Install-10

Click on Install to proceed.

Install-11

Click on Finish to exit Instalation wizard, your Jet is now installed with above provided configuration.

Install-12

Next Step is to Activate your Jet Professional.

From Jet Tab on Ribbon select Activate Jet Professional.

choose the desired option.

Install-13

Enter your activation code and click on Next.

Install-14

Copy the message and send to the mentioned e-mail id and click Next.

Install-15

Close to exit.

Wait for the Activation Token, it may take upto 24 hours to receive mail with this code.

Install-16

If you check your Start Menu you will find these components got installed.

Install-17

Once you receive your Tocken.

Launch Excel, From Jet Tab, Click on Help from ribbon and select Activate License.

Install-18

Select Enter provided Activation token.

Install-19

Copy the Token you received via mail here and click on Activate.

Install-20

If every thing is fine you will receive the Activation Successful message.

Now you are ready to start with using Jet Professional.

I will come up with more details on this in my upcomming posts till then keep exploring and learning.

 

How to Setup Online Bank Feeds in Madeira

You need to be sure : The default company, CRONUS, that launches when you first log in to Project “Madeira” does not have electronic bank feeds enabled. To tryout this feature you must switch to trial Company “My Company“.

In Project “Madeira” you can connect to most of the online banks and download electronic bank feeds for use in bank reconciliation, avoiding tedious, manual reconciliation, reducing errors, and ensuring that your data is refreshed on a frequent basis.

When you log into MyCompany for the first time, a Company Setup wizard will guide you through setting up the basic company information, including using a bank feed service.

Dont forget to select “Use Bank Feed Service” in Company Setup Page to enable this Service.

You can Manage Bank Accounts & Feeds from Bank Account List Page.

BankStatementService-1

If you enable “Use Bank Feed Service” in Company Setup Page, a new section displays in the ribbon as shown in above screenshot with actions so that you can create a new bank account in Project “Madeira” based on the online bank feed, link already existing bank accounts to online bank feeds, unlinking online bank account feeds, or set up automatic download of feeds on a regular schedule.

When you reconcile bank accounts, you can download bank feeds on demand, as well as process automatically downloaded feeds if you have set up already.

In the Payment Reconcilliation Journal, you can import bank statements based on your bank feeds, and Project “Maderia“ will automatically suggest how payments are applied to ledger entries. You can change the application before you post.

Alternatively, you can import bank statements to the Bank Account Reconcilliation window and reconcile the statements with your ledger entries there.

I will come up with more details in my upcoming posts, till then keep practicing and Learning.

 

 

 

 

First update of Project “Madeira” is released – June 2016

What does this update includes?

 

Filter on unprocessed incoming documents

 

The list of incoming documents is now filtered to show only entries that have not been used to create posted documents with.

When documents are posted, the processed flag is set to Yes, such that incoming documents that have been processed into posted documents are filtered out.

You can choose to view all incoming documents in the list if desired, using the show Show All action.

You can also manually switch the processing flag.

 

Office Suite notifications are now enabled in Project “Madeira”

 

In the top right corner, next to the Settings menu, you will notice the bell symbol that you probably already know well from other Office products: That’s the Notifications menu.

Here you will receive notifications such as new mail and calendar reminders directly while working in Project “Madeira”.

 

New extensions, such as Sana Commerce for Project “Madeira” and ChargeLogic Payments that provides payment and credit card processing capabilities.

 

In Project “Madeira”, the Extension Management window lists all available extensions. Some extensions are provided by Microsoft, and other extensions are provided by other companies.

With the first update of Project “Madeira”, extensions have been added by other providers, and Madeira refer to the websites that these companies provide for more information.

Sana Commerce is the integrated B2B e-commerce platform for Project “Madeira” that helps wholesale, distribution and manufacturing companies efficiently run their business, improve their customer service and ultimately generate more revenue through easy online order processing and a 24/7 online access of product information. See the Sana Commerce website.

With ChargeLogic Notify, you can automatically deliver customized, targeted emails directly from Project “Madeira” for invoices, orders, shipments, returns, and sales quotes. Clearly provide the exact information you want with the exact look you want to increase customer satisfaction, promote your brand, and drive business. Using a powerful template system and business rules, you’ll be able to create personalized content and custom designs in an email format and send them to all parties associated with a communication. See the ChargeLogic website. .

 

For further details checkout Link and this Link.

 

 

Multilanguage across Conflicting Text Encoding Formats

For more details please see my earlier posts:

Managing Multilanguage support in Navision Overview

How do I translate my ResX Files?

Working with Partner Translation Toolkit

To support users with translated strings across conflicting text encoding formats, you must save the translations to a text file in UTF-8 text encoding format.

This converts the file to Unicode, which Microsoft Dynamics NAV Development Environment cannot import. Instead, you add the files to a dedicated Translations folder on the Microsoft Dynamics NAV Server computer.

The default location of this folder is

C:\Program Files\Microsoft Dynamics NAV\90\Service\Translations.

When you have more than one service instance, there is a Translations folder for each service instance, such as

C:\Program Files\Microsoft Dynamics NAV\90\Service\Instances\MyInstance\Translations.

Microsoft Dynamics NAV Server adds any strings in text files that you place in the relevant Translations folder to the metadata for Microsoft Dynamics NAV.

To add translated strings for a conflicting text encoding format:

In the development environment, export the strings for the objects that you want to translate.

Translate-1

Select the Objects you wish to add translation, Export and save as text file.

Translate the strings in the resulting text file into desired Language by using your preferred translation process.

Translate-2

I have translated following Captions in Khmer language:

  1. For Field Name & Search Name in Table Customer (18)
  2. TextConstant in Report CustList (50000) to display Caption for Name & Search Name
  3. Caption for User defined variable in Page Customer Card (21)

When translations are complete, save the translated strings into a text file in the UTF-8 text encoding format. The extension of the file must be .txt.

It is recommend that you remove the other Language strings from the Unicode file before you copy it to the Microsoft Dynamics NAV Server computer.

Microsoft Dynamics NAV Server queries the Translations folder for updated strings, and for performance reasons the folder should only contain strings that you cannot import into the development environment because of conflicting codepages.

Copy the UTF-8 file to the equivalent of

C:\Program Files\Microsoft Dynamics NAV\90\Service\Translations

on the Microsoft Dynamics NAV Server computer.

When you have more than one service instance, there is a Translations folder for each service instance, such as

C:\Program Files\Microsoft Dynamics NAV\90\Service\Instances\MyInstance\Translations.

Restart the Microsoft Dynamics NAV Server instance.

Microsoft Dynamics NAV Server adds the translated strings in the file to the metadata store for the Microsoft Dynamics NAV deployment.

Now Users of this Microsoft Dynamics NAV Server session can now change the user interface language from English to required Language.

The metadata store is updated whenever you add new strings to the Translations folder and then restart the Microsoft Dynamics NAV Server service instance. Cached strings are not deleted from the metadata store when you restart the service instance.

 

Let us see the effect of this translation. Let’s run the RTC to see the net effect of same.

[A] Customer List in English However Data Stored in Khmer Language

Translate-3

B] Two Captions Changed in Khmer Language for Name & Search Name

Translate-4

[C] Customer Card in English Language. Selected Captions are changed in Khmer Language

Translate-5

[D] Caption Changed for Name & Search Name to Support Khmer Language also for Field not available in Table the Test Caption

Translate-6

[E] Report Caption in English Language however data in Khmer Language

Translate-7

[F] Report Caption Changed to Khmer Language for Name & Search Name

Translate-8

You can manage Languages using above trick for translate strings across conflicting text encoding formats.

Will comeup with more details in my upcomming posts.

 

Working with Partner Translation Toolkit

In my earlier post I have given the overview of Managing Multilanguage support in Navision continuing from same today I will discuss about how to create Language Module for the Languages not available from Microsoft.

Although still we will not be having direct support for all Languages but using this process you can create one.

To be very fair it will not be easy task for all Languages but for few it could help you much to get you work done with little ease.

See few helpful links which will help you getting done your task:-

Platform strings maintained in managed assemblies and fin.stx and fin.etx files

Configuring Microsoft Dynamics NAV Help Server

To work with Partner Translation Toolkit you will require below, make sure you have all before you start with using this Tool:

  1. Visual Studio
  2. WiX Toolset
  3. Microsoft Translator for ResX
  4. Azure Data Market account
  5. Microsoft Translator data service subscribed
  6. Your NAV License File
  7. Finally your efforts

Visual Studio:

If you don’t have make sure you install the latest version of the same.

WiX Toolset:

You will require the WiX Toolset to start with you can download from here. Install WiX Toolset version 3.8 or 3.9

PTT-1

Install the WiX Toolset according to the instructions. In my case it is already installed on my system so getting option for Uninstall.

Building the project you require that you have the WiX Toolset version 3.8 or 3.9 installed on the computer.

Microsoft Translator for ResX:

See my previous post for more details here.

Azure Data Market account / Microsoft Translator data service:

See my previous post for more details here.

Steps to get ready for Translation tool:

See my previous post for more details here. 

Let’s start with building our project:

Step -1:

Run the “Microsoft.MCSUK.RESXTranslator.exe” Tool

See my previous post for more details here.

Step -2:

Run the “Visual Studio” with opening project solution PartnerTranslations.sln

PTT-8

You will see all the projects discussed above is having their own folder in this solution.

Add your all the translated resx files obtained in Step-1 post Translation to respective projects.

PTT-9

Right click on the project folder and choose Add and then Existing Item.

Select the resx file which we translated in Step-1.

In my case I select “Common.Language.Lang.hi-IN.resx”

Similarly you will add these translated files to your all other projects. Be cautious few may have 2-3 files add them all.

PTT-10

The properties of the installation determine which folders are created during the installation of the language packs and what files are placed in the folders. The properties can be found in the Locals.wxi file located in the root directory of the translation kit. Open the Locals.wxi file and change the following properties:

• CountryRegionCode, to one of the country/region codes in Globals.wxi or create a new.

• ModuleLanguage, to the language of your choice.

• LocalLangFolder, to the .Net culture of the satellite assemblies.

• LocalIsoFolder, to the three letter ISO code for your language.

PTT-11

PTT-12

Step -3:

Build the project PartnerTranslations.sln

To build the PartnerTranslation solution from inside Visual Studio, choose Build Solution from the Build menu. This will pick up all translated artifacts, and create three installer files (.msi):

  • Server.msi – Located in the Server\Bin\Debug folder.
  • RTC.msi – Located in the RTC\Bin\Debug folder.
  • WebClient.msi – Located in the WebClient\Bin\Debug folder.

Step-4:

Copy your Language Module Files and install on desired Server & Client

PTT-13

Install – Add your language pack to the W1 version

If have not already done so, install the W1 version of Microsoft Dynamics NAV 2016 from the product media.

Install the new language Pack

Next, install the new language pack on the same computer. To do this, select and click each of the three .msi files listed below, one after the other. The order is not significant:

  • Server\Bin\Debug\Server.msi
  • RTC\Bin\Debug\RTC.msi
  • WebClient\Bin\Debug\WebClient.msi

Each installer quickly shows a dialog, which disappears when the installer has completed.

The language pack is now installed, but you must make some final configuration.

I will comeup with more details in my next posts.

 

How do I translate my ResX Files?

In my earlier post I have given the overview of Managing Multilanguage support in Navision continuing from same today I will discuss about how to translate the resx files for the Languages not available from Microsoft. 

Microsoft Translator for ResX:

To translate resx file you require to download Microsoft Translator for ResX you can use this link to download.

This will help you to translate your required .resx files

Azure Data Market account / Microsoft Translator data service:

You will need an Azure Data Market account, subscribe to Microsoft Translator data service and a register a developer application in order to use the tool.

You can start setting this up here: https://datamarket.azure.com/developer/applications/

Microsoft Translator is a service on the Windows Azure Marketplace that translates text between many languages. This is a billed service that comes with many different pricing plans. For example, one plan allows the translation of 2,000,000 characters per month for free.

PTT-2

Steps to get ready for Translation tool:

  1. Get an account on the Azure Data Market with your Microsoft Live ID.
  2. Login into the Azure Data Market (ADM).
  3. Subscribe to the Microsoft Translator Service
  4. Create an application on top of this service in order to use the service in the ResX Translator tool.
  5. Go the developer application registration
  6. Choose the Register button to create a new application.
  7. Enter your information and choose the Create button.

Make sure you note your Client ID and Client Secret, you will need this if you wish to Translate Resx files using Microsoft Translator Service.

If you remember I have shared the link from where you can download Translation Tool. You will require Customer/Partner Source.

Download the Translation Tool (NAV2016PartnerTranslationsToolkit) and extract the zip file.

Scan the extracted Folder here few important files which will help identifying purpose of these files:

  1. Microsoft.MCSUK.RESXTranslator.exe
  2. Microsoft.MCSUK.RESXTranslator.exe.xml
  3. NAV 2016 Creating Custom Platform Translations.pdf
  4. PartnerTranslations.sln

PTT-3

Each project contains the platform resource files (.resx) for all languages shipped by Microsoft.

The Visual Studio solution file, PartnerTranslations.sln, contains a project for each of the platform assemblies that contain translatable resources. In order to create a custom translation, you add the respective resource files with custom translations to the respective project.

Let us see the directory structure of “NAV2016PartnerTranslationsToolkit\Microsoft.Dynamics.Nav.Language” similar structure is for other projects too.

PTT-4

For detailed help you can refer to “NAV 2016 Creating Custom Platform Translations.pdf” file.

Let’s start with translating our resx files:

Run the “Microsoft.MCSUK.RESXTranslator.exe” Tool

PTT-5

Switch to Advanced Tab.

Enter the Client ID and Client Secret obtained in above step when we registered the Application.

Click on Save.

PTT-6

Switch to Single File Tab.

Browse the .resx file for source language in my case if have selected “Common.Language.Lang.en-US.resx

Translate To choose desired language available from the drop down. In my case I have selected “Hindi”.

Select the Language 3 char code in my case I have selected “hi-IN [HIN] Hindi (India)

Click on Translate Now.

Once resx file is translated you will get the summary of result, click ok to return.

Similarly you translate the rex files for each projects listed above.

 

PTT-7

Post this step you are ready with all of you resx file translated to desired language.

 

Managing Multilanguage support in Navision Overview

language

Microsoft Dynamics NAV is Multilanguage enabled, which means that you can display the user interface (UI) in different languages.

A Multilanguage version of Microsoft Dynamics NAV is not the same as a localized version.

  • A localized version is a version that is adapted to a local market. All text that is displayed to the user is translated into the local language, and all functional areas are adapted to the requirements of the local market.
  • A Multilanguage version is a localized version that you can run in different languages, but all local functionality remains the same.

 

Language Module:

To be able to run a localized version in multiple languages, you must install language modules.

Language Module contains translated text strings of Logs & error reporting for:

  • Translated strings for the UI in the Microsoft Dynamics NAV Windows client.
  • Translated strings for the database.
  • Translated strings for Microsoft Dynamics NAV Server, such as for logs and error reporting.
  • Translated strings for the Microsoft Office Outlook Add-in for Microsoft Dynamics NAV.
  • Translated strings for charts on Role Centers in the Microsoft Dynamics NAV Windows client.
  • Localized versions of the client Help.

Language Modules are Binary Files which can’t be changed by any external tools for this you will require Partner Translation Tool Project and Visual Studio.

You can install language modules so that you can view text in the user interface in different languages.

Once you have installed a language module, you can select that language on the Select Language page in the UI to change the language of all text that is displayed in the UI in captions for text boxes, on command buttons, in menus, and so on.

Imp: When you change the language of Microsoft Dynamics NAV, you are not changing the language of the data that is stored in Microsoft Dynamics NAV. Changing the text that is stored as application data is not part of the language modules.

When you install a language module, a subdirectory for the language is created in the Microsoft Dynamics NAV directory structure. The .stx, .etx, .chm, and .hh files for each language are automatically installed in the subdirectory. The name of the subdirectory is the three-letter language code (Abbreviated Name) that is used by Windows for the particular language.

You can use this link to access NAV 2016 downloads for Available – Product, Translation Tool & Language Modules. https://mbs.microsoft.com/customersource/Global/NAV/downloads/product-releases/msdnav2016download

 

There are 3 main parts for creating translations that works in Dynamics NAV.

  1. Translate the platform by translating the resource file for each DLL file.
  2. Translate all the captions by adding a new language into captionML in each object
  3. Localize development environment by translating .stx and .etx files. These 2 files have to be sent to the Microsoft regional office and sealed by Microsoft. (Only required if you want the Development Environment to be in Unsupported Language as well)

 

Common available resources for supported/available Language Module.

To work with Language Modules what else you required to know about: You can check below links on MSDN.

  1. Windows Language Virtual Table
  2. How to: Install Language Modules
  3. How to: Add Translated Strings By Importing and Exporting Multilanguage Files
  4. How to: Add Translated Strings By Using the Multilanguage Editor
  5. How to: Uninstall Language Modules
  6. How to: Delete Translated Strings
  7. Multilanguage Development
  8. Viewing the Application in Different Languages

 

Translated User Interface Strings:

In Microsoft Dynamics NAV, the user interface includes the following types of translatable user interface strings:

Captions for application objects, such as pages, tables, reports, option fields, icons, menus, and so on, that are defined in the CaptionML property for an object. Text messages that are defined in the development environment, such as text constants and error messages that are defined in the C/AL Globals window or the C/AL Locals window.

Text messages and strings that are defined in Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Windows client.

To add a language to the text messages that are defined in the resource files for Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Windows client, special tools are required.

You can manage translations by using text files. In the development environment, you can export all strings for the specified objects to a text file, translate the strings in a translation tool of your choice, and then import the new translations. Then, when you compile the updated objects, the new translations are available to users in the Microsoft Dynamics NAV Windows client.

 

Multilanguage across Conflicting Text Encoding Formats:

To support users with translated strings across conflicting text encoding formats, you must save the translations to a text file in UTF-8 text encoding format.

This converts the file to Unicode, which Microsoft Dynamics NAV Development Environment cannot import. Instead, you add the files to a dedicated Translations folder on the Microsoft Dynamics NAV Server computer.

The default location of this folder is:

C:\Program Files\Microsoft Dynamics NAV\90\Service\Translations.

When you have more than one service instance, there is a Translations folder for each service instance, such as:

C:\Program Files\Microsoft Dynamics NAV\90\Service\Instances\MyInstance\Translations.

Microsoft Dynamics NAV Server adds any strings in text files that you place in the relevant Translations folder to the metadata for Microsoft Dynamics NAV.

 

To add translated strings for a conflicting text encoding format:

In the development environment, export the strings for the objects that you want to translate.

Translate the strings in the resulting text file into desired Language by using your preferred translation process.

When translations are complete, save the translated strings into a text file in the UTF-8 text encoding format. The extension of the file must be .txt.

It is recommend that you remove the other Language strings from the Unicode file before you copy it to the Microsoft Dynamics NAV Server computer.

Microsoft Dynamics NAV Server queries the Translations folder for updated strings, and for performance reasons the folder should only contain strings that you cannot import into the development environment because of conflicting codepages.

Copy the UTF-8 file to the Microsoft Dynamics NAV Server computer.

C:\Program Files\Microsoft Dynamics NAV\90\Service\Translations

When you have more than one service instance, there is a Translations folder for each service instance, such as:

C:\Program Files\Microsoft Dynamics NAV\90\Service\Instances\MyInstance\Translations.

Restart the Microsoft Dynamics NAV Server instance.

Microsoft Dynamics NAV Server adds the translated strings in the file to the metadata store for the Microsoft Dynamics NAV deployment.

Now Users of this Microsoft Dynamics NAV Server session can now change the user interface language from English to required Language.

The metadata store is updated whenever you add new strings to the Translations folder and then restart the Microsoft Dynamics NAV Server service instance. Cached strings are not deleted from the metadata store when you restart the service instance.

I will comeup with more details in my upcomming post soon.

Cumulative Update 19 for Microsoft Dynamics NAV 2015 – Released in May 2016

Cumulative Update 19 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015.

The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

  •   AU – Australia
  •   AT – Austria
  •   BE – Belgium
  •   CH – Switzerland
  •   CZ – Czech Republic
  •   DE – Germany
  •   DK – Denmark
  •   ES – Spain
  •   FI  – Finland
  •   FR – France
  •   IS – Iceland
  •   IT – Italy
  •   NA – North America
  •   NL – Netherlands
  •   NO – Norway
  •   NZ – New Zealand
  •   RU – Russia
  •   SE – Sweden
  •   UK – United Kingdom

Note: You must convert the database if you are upgrading to this cumulative update from a cumulative update earlier than Cumulative Update 9 (build 41779). For more information, see Converting a Database in Help for Microsoft Dynamics NAV.

Note: To enable customized translation of profiles, a number of actions are now available on the Profile List page. You can export and import resource files to enable translation for one or more profiles. The steps to install and uninstall language modules have also been modified. For more information, see How to: Install Language Modules, How to: Uninstall Language Modules, and How to: Export, Edit, and Import Translated Profile Strings in Help for Microsoft Dynamics NAV.

Where to find Cumulative Update 19

You can download the cumulative update from KB 3157490 – Cumulative Update 19 for Microsoft Dynamics NAV 2015 (Build 45813).

Warning

Before you install a cumulative update in a production environment, take the following precautions:

  1. Test the cumulative update in a non-production environment.
  2. Make a backup of the system or computer where the cumulative update is to be installed.

Additional Information

For information about how to install the cumulative update, see How to Install a Microsoft Dynamics NAV 2015 Cumulative Update.

For information about how to work around a recent process change, see How to Get Back the ‘Hotfix Directories’ from NAV 2015 Cumulative Update 1.

For a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2015.

 

Previous Older Entries

Important

Most of the contents you find in this blog will be either inherited from MSDN or Navision Developer IT Pro Help. Some places images are also directly taken from these sites. Purpose is simple to try those stuffs and re-produce adding few things as per my understanding to make easy understanding for others and quick reference.

Here nothing under my own brand or authorship of the content. At any point of time we are just promoting Microsoft stuffs nothing personnel with same.

Hope stuffs used here will not violate any copyright agreement with them. In case by mistake or in-intestinally it happens and the Microsoft feels these should not be used Microsoft have full right to inform me about same and will be glad to take down any such content which may be violating the norms.

Purpose is to promote Navision and share with community.

FB Profile

Like FB Page

%d bloggers like this: