Tag: Dynamics

Cumulative Updates, Tip & Tricks

Cumulative Update 8 for Microsoft Dynamics NAV 2016 released in June 2016

Ashwini Tripathi

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

Where to find Cumulative Update 8

You can download the cumulative update from KB 3166287 – Cumulative Update 8 for Microsoft Dynamics NAV 2016 (Build 46045).

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 2016 Cumulative Update.

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

Cumulative Updates, Tip & Tricks

Cumulative Update 20 for Microsoft Dynamics NAV 2015 released in June 2016

Ashwini Tripathi

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

Where to find Cumulative Update 20

You can download the cumulative update from KB 3166286 – Cumulative Update 20 for Microsoft Dynamics NAV 2015 (Build 46054).

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.

Cumulative Updates, Tip & Tricks

Cumulative Update 32 for Microsoft Dynamics NAV 2013 R2 released in June 2016

Ashwini Tripathi

Cumulative Update 32 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2.

Where to find Cumulative Update 32

You can download the cumulative update from KB 3166278 – Cumulative Update 32 for Microsoft Dynamics NAV 2013 R2 (Build 46057).

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 more information about cumulative updates for this version, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

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

For a list of all hotfixes included in cumulative updates for this version, see the following CustomerSource and PartnerSource pages:

CustomerSource:

PartnerSource

Cumulative Updates, Tip & Tricks

Cumulative Update 39 for Microsoft Dynamics NAV 2013 released in June 2016

Ashwini Tripathi

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

Where to find Cumulative Update 39

You can download the cumulative update from KB 3166277 – Cumulative Update 39 for Microsoft Dynamics NAV 2013 (Build 46056).

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 a list of all cumulative updates for this version, see Released Cumulative Updates for Microsoft Dynamics NAV 2013.

For a list of all hotfixes included in cumulative updates for this version, see the following CustomerSource and PartnerSource pages:

CustomerSource:

PartnerSource:

 

Corfu Navision 2016, Development Tips, How To, Information, Instalation & Configuration, Server, Tip & Tricks

Multilanguage across Conflicting Text Encoding Formats

Ashwini Tripathi

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.

 

Cumulative Updates, Functional Tips, How To, India Localization, Information, Tip & Tricks

Krishi Kalyan Cess Feature for Microsoft Dynamics NAV 2013 R2 for India Released

Ashwini Tripathi

Government has introduced a new Cess called ‘Krishi Kalyan Cess (KKC)’ in Finance Act 2016 which will take effect from 01-Jun-2016. It is imposed on all taxable Services at the rate of 0.5%. KKC is not a Cess on Service Tax but it is a tax on taxable services in addition to Service tax. It would be calculated in the same way as Service Tax is being calculated.

Download

IN7.1_TFS167310 – Krishi Kalyan Cess [9.04 MB – EXE]

Installation

Before this update can be installed, the following prerequisites are required:
Microsoft Dynamics ® NAV 2013 R2 India
Pre-requisites

  • NAV 2013 R2 RTM Database (Version 7.10.35473)
  • Import below Hotfixes sequentially
No. TFSID Fixes Description
1 TFS353595 TDS Zero Percent
2 TFS354411 FVU 3.9-4.1 and TDS Zero Pct
3 HF377555 GL Inconsistency
4 TFS160375 Swachh Bharat Cess

 

License Requirement

No new objects have been added through this update. Licensing refresh is not required.

 

Setup

The following fields are added to Service Tax Setup , setup values given below

S. No Field Description Value
1. KK Cess % 0.5
2. KK Cess Payable Account Balance  Sheet Account under Liabilities and Account Type = Posting
3. KK Cess Payable Interim Balance  Sheet Account under Liabilities and Account Type = Posting
4. KK Cess Receivable Interim Account Balance  Sheet Account under Assets and Account Type = Posting
5. KK Cess Receivable Account Balance  Sheet Account under Assets and Account Type = Posting
6. KK Cess Expense Account Income Statement Account and Account Type = Posting

For detailed information you can check this Link.

 

Development Tips, Functional Tips, How To, Maderia, Tip & Tricks

Setup Send Documents by Email in Madeira

Ashwini Tripathi

To enable emails from within Project “Madeira”, start the Set Up Email assisted setup on the Home page. We have already seen this in our previous post, you can find it here.

To offer your customers to pay for sales electronically using a payment service, such as PayPal, you can also have the PayPal information and hyperlink inserted in the email body. We have already covered this in our previous post, you can find it here.

From all supported documents, you initiate emailing by choosing the Send action, on posted documents, or the Post and Send action, on non-posted documents.

Let us Setup document-specific email body for sales invoices.

From the search page find Report Selections Sales:

SetupEmail-10

Fill the Value as shown in below screen in same sequence.

SetupEmail-11

If you want to offer customers to pay for sales electronically, you can set up the related payment service, such as PayPal, and then have the PayPal information and hyperlink inserted in the email body as well. We have already covered this in our previous post, you can find it here.

Will come up with more details & feature explaination in my upcomming posts.

 

Development Tips, Functional Tips, How To, Maderia, Tip & Tricks

How do I process Sales Return? – In Maderia

Ashwini Tripathi

We have seen in our previous post the feature where if a posted sales invoice has not yet been paid, then you can use the Correct or Cancel functions on the posted sales invoice to automatically reverse the involved transactions.

There could be the situation where customer wants partial refund or return of sales.

You can create the Credit Memo from the Posted Sales Invoice, which will create the Credit Memo for you and leave to you to modify and post the credit memo.

Most fields on the sales credit memo header are filled with the information from the posted sales invoice. You can edit all the fields, with new information that reflects the return agreement.

You can apply the Customer Entries via selecting the line with the posted sales document that you want to apply the sales credit memo to.

The posted sales documents that you applied the credit memo to are now reversed, and a refund payment can be created for the customer.

The sales credit memo is removed and replaced with a new document in the list of posted sales credit memos.

Let us see how we can achieve this in Madeira.

 

CorrectCancelSalesInvoice-12

Select the Sales Invoice and open it for action.

CorrectCancelSalesInvoice-13

Select Create Corrective Credit Memo.

CorrectCancelSalesInvoice-14

Perform the required correction and choose Apply Entries.

CorrectCancelSalesInvoice-15

Select the document to which you want this Credit Memo to be adjusted.

CorrectCancelSalesInvoice-16

Once Application is done, Post the Credit Memo.

Respond to Yes to post the Credit Memo.

Respond to Yes to Open the posted Credit Memo.

CorrectCancelSalesInvoice-17

This is the posted Credit Memo for the Invoice.

Let us check the Ledger for this Customer:

CorrectCancelSalesInvoice-18

Here you can see the net effect of the Credit Memo on Invoice.

Thats all for this post will come up with more features and details in my upcomming posts.

 

 

Development Tips, Functional Tips, How To, Maderia, Tip & Tricks

Correct or Cancel Unpaid Sales Invoices – in Madeira

Ashwini Tripathi

Sometimes Invoices are posted in mistake or customer demands changes in invoice after posting.

Once the payment is initiated, partially or fully paid correction or cancellation is not allowed from Posted Sales Invoice itself. In such case you need to follow traditional way of doing so by passing Sales Credit Memo to Cancel the Sale and reimburse to customer manually.

 

What happens when you select Correct Action?

The Posted Invoice for which you say correct that invoice gets cancelled and new Sales Invoice with same information is created.

Naturally to maintain the integrity of data new Sales Invoice is created with new Document No.

A Sales Credit Memo for previous Invoice is created to void the effect of initial posted Sales Invoice.

The Canceled and Paid is marked on initial posted Sales Invoice document.

 

What happens when you select Cancel Action?

The Posted Invoice for which you say correct that invoice gets cancelled.

A Sales Credit Memo for previous Invoice is created to void the effect of initial posted Sales Invoice.

The Canceled and Paid is marked on initial posted Sales Invoice document.

 

Important Points:-

If the Canceled check box is selected, then you cannot correct or cancel the posted sales invoice because it has already been corrected or canceled.

Once the payment is initiated, partially or fully paid correction or cancellation is not allowed from Posted Sales Invoice itself.

 

Let us see how it works in Madeira:-

Login with your credentials to Madeira project.

 

CorrectCancelSalesInvoice-1

From the Navigation Bar choose Sales.

CorrectCancelSalesInvoice-2

Select Posted Sales Invoice. And choose to open the posted Sales Invoice.

CorrectCancelSalesInvoice-3

Select Correct to Modify the Invoice.

CorrectCancelSalesInvoice-4

Select Yes to continue with the process.

CorrectCancelSalesInvoice-5

Make the required modification to the Invoice and post it.

CorrectCancelSalesInvoice-6

Select Yes to continue with posting.

CorrectCancelSalesInvoice-7

Select Yes to continue.

CorrectCancelSalesInvoice-8

This is new modified Invoice that got posted.

Let us move to the original Invoice which we corrected.

CorrectCancelSalesInvoice-9

Select Show Corrective Credit Memo.

CorrectCancelSalesInvoice-10

This is the Credit Memo posted against the Invoice which we corrected.

CorrectCancelSalesInvoice-11

You can see the Closed and Canceled is Marked to TRUE.

 

 

Corfu Navision 2016, Development Tips, How To, Information, Instalation & Configuration, License, Server, Tip & Tricks, Virtual

Working with Partner Translation Toolkit

Ashwini Tripathi

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.