7 Doubts You Should Clarify About Multiple Language Solution In NAV

Is your Solution MULTI Language Acceptable?

Hi All,

This post is about  providing your solution of Nav to be implemented in multi langauages.

While creating reports in NAV we have many a times used Hard Code Error  which resolves solutions but the long term impact of such cases I want to share with my readers.

So the summarise post is below :- 

How to achieve Multi Language Implementation Solution?

We must provide every error , message , confirmation in TEXT CONSTANT and we must provide another language in Caption ML Property of NAV.

More about property is Here.

Where we must use it?

1. Object Name

2. Function Name

3. Function Variable

4.Option Type 

5.Control Names.

 Comment,CAPTIONML,OPTIONML,Instruction,Instruction Tool ML.

Rules :-

Always use text constants and avoid hard code while defining ERROR,MESSAGE,CONFIRM,STRMENU,OPTION,DATEFORMULA

Alway try to use FIELDCAPTION,TABLECAPTION,STRSUBSTNO to retrieve caption values for comparing object names.

Thanks.

Please subscribe our post and follow us below to getmore valuable updates to develop MS Dynamics NAV Solutions.

The Miracle Of Hook In Ms Dynamics Navision 2016 and 2017?

Why to use Hooks in NAVISION ?

Hooks are the another ways to implement customisation in NAV 2016 and above.

Hooks Advantage :-

1. It increases Transparency.

      2. It increases Testability.

      3. It creates easy Upgradation of NAV versions.

      4. Separate Codunit for each objects. and there will be only a reference in base objects.

      5. Impact of Customisation will be minimum.

How to implement Hooks?

Step1.

Create a new codeunit which will be a parent codeunit and will be used for all customisation in NAV.

Step2.

Naming Conventions of HOOK

Microsoft Suggests Codeunit Process Name_HOOK for Eg. SIH_HOOK For Sales Invoice Header customisations.

Step3.

Create the hook and take an example to update a field and validate it before customisations.

for Example

Step4.

Reference it in Sales Post Codeunit.

Step5.

Implement all business logic in Hook Codeunit.

Summarize:-

Basically , it is another method suggested by MIcrosoft to write all code in one place so that implementation becomes easy to undertand and working smoothly.

To deploy Apps on Microsoft Partner Source you need to follow these guidelines provided by microsoft.

Thanks.

I hope this will surely hlp all my juniors to work and learn fastly, Please share my blog and comment below if you want another post or querry from my side.

10 Things Nobody Told You About Nav Coding Guidelines.

How to start Coding in MS Dynamics NAV?

Hi All,

This post is just a starting of a new age of NAV Extension and coding guidelines to develop new

 requirements. So it is for all the NAV developers all over the world to follow these codelines.

Why we as NAV Technical Consultant need these guidelines?

Now requirements of our clients and developments have been changed a lot with technical 

background so we need all the changes to be deployed with latest functionalities.

To implement these changes you must have to leearn these codelines and guides.

Where can we get these coding guidelines?

You can get these coding guide lines from Microsoft Wiki Nav Community.

NAV Community For coding guidelines.

Sumarised guidelines for NAV Technical Consultant.

1. NAV Technical Consultant must understand these topics clearly.

More References to be followed:

Waldo's Reference blog for NAV Technical consultant.