Nandesh Gowda

Microsoft Dynamics NAV 2018 Released

2017-12-01T21:33:00.001+05:30

Hi All,

Microsoft Dynamics NAV 2018 has been released.

Please use below link to download the same

https://mbs.microsoft.com/partnersource/global/deployment/downloads/product-releases/msdnav2018download

You can refer below link to see what's new in NAV 2018
https://mbs.microsoft.com/Files/partner/NAV/Readiness_Training/ReadinessTrainingNews/WhatsNewDynamicsNAV2018.pdf

Thanks & Regards,
Nandesh Gowda

NAV 2016 CU 22 Released

2017-08-09T08:07:00.000+05:30

Hi All,

NAV 2016 CU 22 has been released, please find below download link.

https://support.microsoft.com/en-ae/help/4037308/cumulative-update-22-for-microsoft-dynamics-nav-2016-build-48992

Thanks & Regards,
Nandesh Gowda

GST for NAV 2013 R2

2017-05-24T09:00:00.000+05:30

Hi All,

Below is the Link for GST patch for NAV 2013 R2

https://mbs.microsoft.com/customersource/Global/NAV/downloads/tax-regulatory-updates/GSTTAXNAV2013R2IN

Thanks & Regards,
Nandesh Gowda

GST- India Released for NAV 2016

2017-03-06T22:35:00.002+05:30

Hi All,

Microsoft has released GST- Goods & Service Tax- India which is soon going to be implemented in India with proposed date of 1st July, 2017.

The GST is included with the release of NAV 2016 Cumulative Update 17. Below is the download link for the same.
https://www.microsoft.com/en-us/download/details.aspx?id=54804

Below is the Link to White paper for GST-India
https://mbs.microsoft.com/partnersource/global/deployment/downloads/tax-regulatory-updates/nav2016gstindia

Thanks & Regards,
Nandesh Gowda

Cumulative Update 17 released for NAV 2016

2017-03-06T22:16:00.001+05:30

Hi All,

Microsoft has released Cumulative Update 17 for NAV 2016.

Below is the link to download page for the same.
https://www.microsoft.com/en-us/download/details.aspx?id=54804

Thanks & Regards,
Nandesh Gowda

Application Worksheet NAV

2017-02-04T21:04:00.001+05:30

Hi All,

You can view and change item application entries that are automatically created between item ledger entries during item transactions.

When you post a transaction where items are moved in or out of inventory, an item application is created between each inventory increase and inventory decrease.

These applications determine the flow of costs from the goods that are received in inventory to the cost of goods going out of inventory.

Because of the way the unit cost is calculated, an incorrect item application could lead to a skewed average cost and a skewed unit cost.

You can undo an application or reapply the item ledger entries. Below scenario's may require you to do so.

You have forgotten to make a fixed application.
You have made an incorrect fixed application.
You have to return an item to which a sale has already been applied.

You can view the Applied Entries for an Item Ledger Entry by clicking on the Application Worksheet--> Applied Entries.
Also you can remove the Application by clicking on the Remove Application action.

To Reapply an item application: Click on Unapplied Entries and then select the Entry against which to apply and press OK

If possible, use a document to reapply an item ledger entry. For example, if you must make a purchase return of an item to which a sale has already been applied, you can reapply by creating and posting the purchase return document by using the correct application in the Appl.-to Item Entry field on the purchase return line.

You can use the Get Posted Document Lines to Reverse function or the Copy Document function in the purchase return document to make this easier. When you post the document, the item ledger entry is automatically reapplied.

If you cannot use a document to reapply, such as when you have to correct a fixed application, then use the Application Worksheet window to correct an application.

Warning
The following are important considerations to remember when you are working with the application worksheet: You should not leave application entries unapplied for long periods of time because other users cannot process the items until you reapply the application entries or close the Application Worksheet window. Users who try to perform actions that involve a manually unapplied application entry receive the following error message:“You cannot perform this action because entries for item XXX are unapplied in the Application Worksheet by user XXX.” You should only reapply item ledger entries during nonworking hours to avoid conflicts with other users who are posting transactions with the same items. When you close the application worksheet, Microsoft Dynamics NAV performs a check to make sure that all entries are applied. For example, if you remove a quantity application but do not create a new application, and then you close the application worksheet, a new application is created. This helps keep the cost intact. However, if you remove a fixed application, a new fixed application is not automatically created when you close the worksheet. You must do this manually by creating a new application in the worksheet. It is possible to remove applications from more than one entry at a time in the application worksheet. However, because applying entries affects the set of entries that are available for application, you cannot create an application for more than one entry at a time. The application worksheet cannot make an application in the following situation: If there is not enough quantity on stock to apply, the application worksheet cannot make an application when you are trying to apply an inventory decrease entry without item tracking information to an inventory increase entry with item tracking information.

Warning

The following are important considerations to remember when you are working with the application worksheet:

You should not leave application entries unapplied for long periods of time because other users cannot process the items until you reapply the application entries or close the Application Worksheet window. Users who try to perform actions that involve a manually unapplied application entry receive the following error message:“You cannot perform this action because entries for item XXX are unapplied in the Application Worksheet by user XXX.”
You should only reapply item ledger entries during nonworking hours to avoid conflicts with other users who are posting transactions with the same items.
When you close the application worksheet, Microsoft Dynamics NAV performs a check to make sure that all entries are applied. For example, if you remove a quantity application but do not create a new application, and then you close the application worksheet, a new application is created. This helps keep the cost intact. However, if you remove a fixed application, a new fixed application is not automatically created when you close the worksheet. You must do this manually by creating a new application in the worksheet.
It is possible to remove applications from more than one entry at a time in the application worksheet. However, because applying entries affects the set of entries that are available for application, you cannot create an application for more than one entry at a time.
The application worksheet cannot make an application in the following situation: If there is not enough quantity on stock to apply, the application worksheet cannot make an application when you are trying to apply an inventory decrease entry without item tracking information to an inventory increase entry with item tracking information.

Thanks & Regards,
Nandesh Gowda

Create Item from Description NAV

2017-02-04T21:04:00.000+05:30

Hi All,

NAV can now suggest to create a new item when no item matches the description on sales documents.

Setup is available on Sales & Receivables Setup. The Items will be created based on Item Templates.

System will give a popup when you enter the Item Description if it not matches any of the Item description.

You can choose from the existing Item templates or create a new one.

Item card will open up, you can fill rest of the information and select the newly created item on sales documents.

Thanks & Regards,
Nandesh Gowda

Default Item Quantity NAV

2017-02-04T21:03:00.000+05:30

Hi All,

We can now default Quantity field to 1 for items when you create new sales documents.

The setup is available on Sales & Receivables Setup. Once you select the No. field, quantity will get updated to 1.

Thanks & Regards,
Nandesh Gowda

Defer Revenues and Expenses, Deferral Templates NAV

2017-01-21T19:38:00.000+05:30

Hi All,

To recognize revenues and expenses in periods other than the period in which the transaction is posted, you can use functionality to automatically defer revenues and expenses over a specified schedule.

Deferral functionality is available on sales documents, purchase documents, and in the general journal. The functionality provides benefits, such as:

Reduced time and effort to defer revenues and expenses after transactions are posted.

Easy reporting on deferred amounts for customers, vendors, and G/L accounts.

Here we will discuss on Deferring Expenses pertaining to Advertising for 1 year and how to distribute the Amount to respective period.

1) To set up a G/L account for deferred expenses

Go to Chart of Accounts and create a New G/L Account of Type Balance Sheet , where the deferred expenses will be posted to. Name the account, for example, Prepaid Advertising Expenses.

2) To set up a deferral template

Search for Deferral Template Page and create New Template. Select the G/L Account created in above step to post deferred expenses.

Please refer below table on how to fill in the Deferral template.

Field	Description
Deferral Code	Identify the deferral template.
Description	Describe the deferral template.
Deferral Account	Specify the G/L account that the deferred expenses are posted to.
Deferral %	Specify how much of the total amount will be deferred.
Calc. Method	Specify how the Amount field for each period in the Deferral Schedule window is calculated. You can choose between the following options: Straight-Line: The periodic deferral amounts are calculated according to the number of periods, distributed according to period length. Equal Per Period: The periodic deferral amounts are calculated according to the number of periods, distributed evenly on periods. Days Per Period: The periodic deferral amounts are calculated according to the number of days in the period. User-Defined: The periodic deferral amounts are not calculated. You must manually fill the Amount field for each period in the Deferral Schedule window. For more information, see the “To change a deferral schedule from a purchase invoice” section.
Start Date	Specify when to start calculating deferral amounts. You can choose between the following options: Posting Date: The start date used when calculating deferral amounts is the posting date of the invoice. Beginning of Period: The start date used when calculating deferral amounts is the first day of the accounting period in which the posting date falls. End of Period: The start date used when calculating deferral amounts is the last day of the accounting period in which the posting date falls. Beginning of Next Period: The start date used when calculating deferral amounts is the first day of the accounting period that follows the accounting period in which the posting date falls.
No. of Periods	Specify how many accounting periods the total amounts will be deferred to.
Period Desc.	Specify a description that will be shown on entries for the deferral posting. You can enter the following placeholder codes for typical values, which will be inserted automatically when the period description is displayed. %1 = The day number of the period posting date %2 = The week number of the period posting date %3 = The month number of the period posting date %4 = The month name of the period posting date %5 = The accounting period name of the period posting date %6 = The fiscal year of the period posting date Example: The posting date is 02/06/2016. If you enter “Expenses deferral for %4 %6”, then the description displayed will be Expenses deferral for February 2016.

3) To assign a deferral template to an Item, G/L Account, etc.

Assign the Deferral Template to an Expense Account

4) Create a Purchase Invoice taking the G/L Account to which we tagged Deferral Template.

As soon as we select the G/L Account, the Deferral Code is filled in by default.

Now go to Lines FastTab-->Line --> Deferral Schedule to view the Deferral Calculation.

You can see system has divided the Amount into no of periods we specified in the setup.

You can also change the Deferral Amount here as well on Header or Line and then click Calculate Schedule

5) You can Preview how deferral expenses will be posted to GL. You can see initially the Expense will be posted to Deferral Account and then the expenses are moved to actual Expense Account for each period.

6) Now post the entries, to review posted deferrals run Purchasing Deferral Summary report.

Similarly you can Defer Revenues to the Period of Delivery .
Please refer below link
https://msdn.microsoft.com/en-us/library/mt574363(v=nav.90).aspx

Thanks & Regards,
Nandesh Gowda

Invalid file reference. The path to the file is invalid, or one or more of the referenced schemas could not be found. Configuration Package NAV

2017-01-21T19:37:00.001+05:30

Hi All,

Invalid file reference. The path to the file is invalid, or one or more of the referenced schemas could not be found.

I got above error while trying to export to excel Item Journal Line table from configuration Packages.

After analysing, I was able to identify the field due to which this error was coming. The field name was "Line No"

But the data in that field was fine, after further analysing I realized that while exporting to excel system creates an XML Schema Mapping for all the fields.

The XML Schema Name for standard field "Line No." was "LineNo", so while creating for customized field "Line No" system was throwing this error as the Name was getting conflicted.

So finally we excluded that field and exported the data as it was not a relevant field for us.

Thanks & Regards,
Nandesh Gowda

Inventory Revaluation NAV

2017-01-01T10:32:00.000+05:30

Hi All,

The inventory value of an item can change over time, for example, as a result of damage or age.

If you want to change the inventory value of an item or a specific item ledger entry, you must use the revaluation journal in NAV.

You can also use the revaluation journal to correct incorrect posted documents.

You must first run the Adjust Cost - Item Entries batch job before you revalue the inventory so that all the cost is adjusted.

To update cost of items with costing method as Standard the process is little different.

For ex : To revalue items other than Standard Costing method we can follow below process

Screenshot of Item Card

Go to Revaluation Journal Page

There are two ways of filling in the journal with information about the current, calculated value of the specified item:

You can enter a line manually and link it to an item ledger entry in the Applies-to Entry field. This will change the inventory value of all units of this item ledger entry. It will also change the inventory value of the units that are applied to this item ledger entry, regardless of their posting date.

OR

You can fill in the journal by using the Calculate Inventory Value batch job. This method allows you to specify exactly how the revaluation will change the inventory value of an item or item ledger entry. The revaluation will be valid for entries relating to this item or item ledger entry from the posting date of the revaluation journal.

Using Calculate Inventory Value batch job.

Posting Date : You can set the date on which you want to revalue.

Calculate Per : Whether you need to sum inventory value by Item (Location, variant) or Per Item Ledger Entry.

Update Standard Cost :Select this field if you want the program to update the standard cost on the item card. If the item is in stock on the posting date of the revaluation, a revaluation journal line will be created.

The standard cost on the item card will then be updated when the revaluation journal line is posted. If the item is not in stock on the posting date, then the standard cost on the item card will be updated immediately.

Calculation Base: In this field, you can specify how the revaluation journal will suggest a new value for the Unit Cost (Revalued) field.

The options are:
• : The revaluation journal will suggest the same value as in the Unit Cost (Calculated) field .

• Last Direct Unit Cost: The revaluation journal will calculate the value in the field based on the Last Direct Unit Cost on the Stockkeeping Unit card or the Item card.

• Standard Cost - Assembly List: The revaluation journal will calculate the value in the field based on the bill of materials.

• Standard Cost - Manufacturing : The revaluation journal will calculate the value in the field based on the production BOM.

Now you can change the Unit Cost (Revalued) field with the new value and post the revaluation journal.

Alternatively you can enter revaluation journal manually by selecting the Item No. and Applies-to Entry if you need to correct any single entry.

Once posted we can see the changes on Item card, system will pass a value entry and corresponding journal entries.

Process for Standard Cost Update :

1) Run the Adjust Cost - Item Entries batch job.
2) Run the Post Inventory Cost to G/L batch job.
3) Open the Standard Cost Worksheet and use one or more of the following functions:

Run the Suggest Item Standard Cost batch job.
Review the results and make changes as necessary.
Run the Suggest Work/Mach Ctr Std Cost batch job.
Review the results and make changes as necessary.

4) Run the Roll Up Standard Cost batch job.
5) Review the results and make changes as necessary.
6) Run the Implement Standard Cost Change batch job.

Enter the Posting Date, Document No. and the Item Journal Template & Batch.

7) Review and post the Revaluation Journal, which has been populated with entries from previous step in this process.

Thanks & Regards,
Nandesh Gowda

Item Charges NAV

2017-01-01T10:29:00.002+05:30

Hi All,

Item Charges Functionality is used in NAV to enter/add charges such as Freight, Custom, Insurance, Clearing, etc. which is pertaining to Items and then link the charges to that Item to arrive at the exact cost of that item.

The item charge can be entered on a separate invoice or in the document where the items that the cost relates to are listed.

It is strongly recommended to pass all the expenses related to Item through Item Charges so that you can finally arrive at Landed Cost of the item being purchased instead of expensing it out using G/L Account directly.

Also, you can use Item Charges for any price difference for purchase or sale transactions.

To create a new Item Charge go to Item Charges page as shown below.

Enter the No. and Description and tag the Gen. Prod Posting Group to allow system to pick the expense account for charges.

Here we will create a separate Invoice and load the charge amount to Purchase receipt Lines.

Please create a Purchase Document and select Charge(Item) for Item Charges as shown below.
Enter the Quantity and Amount in Direct Unit Cost.

Now Go to Line and select the Item Charge Assignment Option

You can Load Charges on Purchase, Sales, Transfers and Return transactions.
Here we will load on Purchase Receipt Lines. so click on Get Receipt Lines and select the relevant Purchase Receipt Lines. Once selected click on OK.

System will give option to split the charge amount Equally or based on Amount. If you have Multiple Items or Multiple Purchase Receipts you may need to split the Charge Amount between those Item Lines.

or

Alternatively you can enter Qty to Assign to split the Amount.

After Assigning the Item Charge we will post the document and see the impact of the Item Charge on the main Item.

If you Navigate to the Purchase Receipt on which you loaded the Item Charge Amount , you will see system has created one more Value Entry with the Amount you distributed during assigning item charge. So the Cost of the Item for that particular receipt has increased by the Charge Amount.

Thanks & Regards,
Nandesh Gowda

Power BI reports in Microsoft Dynamics NAV 2017 Role Center

2017-01-01T10:25:00.000+05:30

Hi All,

Today, I will demonstrate how to configure Power BI Services and a Power BI account, as well as add Power BI reports to a user’s NAV 2017 Role Center

1) Setup Azure Active directory to register an application so that it enables on premise application to communicate with Power BI services, Office 365 Exchange Online and other Azure services.

Go to--> Assisted Setup--> Setup Azure Active Directory--> Next

2) We need to register the NAV 2017 application with Azure Directory and obtain the Application ID and Key from Azure Portal so that NAV 2017 can communicate with Azure services.

3) To register NAV 2017 please sign into Azure Portal with your credentials.

Click on Azure Directory Icon --> App registrations --> Add

Name: Give the Name for App Registration
Application Type : Select Native
Redirect URI : Select from Reply URL from the above screen.

Finally click on Create to register the NAV App. It will generate Application ID.

4) Now give Permission to various API's available, in our case Power BI Services.

Click on Required permissions--> Add --> Select an API--> Power BI Services --> Select

Give the required permissions and complete the process

5) Now generate the Key

Give Description, Expires and then Save, it will generate a key.

6) Now come back to Step 2 and enter the Application ID and Key and then Finish the setup.

We registered in Azure Active Directory, and permissions to the Power BI Service API are set, now we are ready to start working with Power BI reports in Dynamics NAV

7) Now go to to Role Center and click on Get Started with Power BI.

8) Click on Authorize Azure Services to give data access permissions to Azure resources.

9) Sign in with your Azure directory credentials and click on Accept to complete the process.

10) Now Power BI Reports are available on your Role Center dashboard.

Select the reports from the list of reports you have created in Power BI.

11) As shown below you can view the report data, move between other reports and expand the view layout.

Thanks & Regards,
Nandesh Gowda

Developing Extensions in Visual Studio Code with New Development environment NAV

2016-12-25T01:29:00.001+05:30

Hi All,

Visual Studio Code and the AL Extension lets you do the following tasks

Create new files for your solution
Get assistance with creating the appropriate configuration and setting files
Use code snippets that provide templates for coding application objects
Get compiler validation while coding
Press F5 to publish your changes and see your code running

Visual Studio Code manages projects by including all files from a directory. Whatever files exist in that directory are then part of your project.

In addition there are two other configuration files; app.json and launch.json. You can define these yourself, possibly by copying the files from sample code or you can have the system autogenerate them for you.

Building the solution (Ctrl+Shift+B) will create the app.json file and publishing (F5) will generate the launch.json file. Within these files, you’ll need to set up some parameters to connect to your server.

Ex: Here we will create an Extension to an Item table with a new field and add a validation to the new field created.

1) First Create a Project Folder and select that Folder from Visual Studio Code. Or you can start from Visual Studio Code and create folder and files from there itself.

2) You can Copy the launch.json and app.json file from other sample projects or else you can allow visual studio to create it automatically during building and publishing the project.

3) Add New file by clicking on New Icon and give it a Name and save it as .al extension. Saving it in .al extension will activate the AL Language Extension for Visual Studio Code. In the same file we will add our code.

4) Now in the Code Editor type in ttableext and the IntelliSense will bring in the code snippet for you.

5) Now change the code to add new field on Item table and similarly add the new field on item card page with validation on it by using page extension.

Below is for table extension

Below is for page extension

6) Now press Ctrl+Shift+B to build the solution and resolve if any errors. It will create .navx extension file.

And press F5 to publish the Package which is created on to NAV server.

7) Now let us verify whether the field has been added from NAV RTC and whether our validation is working. You can also see the published/installed extensions under Extensions Page in NAV RTC.

Note:

Below are the settings available in app.json and launch.json files.

Settings in the app.json file:

Setting	Mandatory	Value
id	Yes	The unique ID of the extension. When app.json file is automatically created, the ID is set to a new GUID value.
name	Yes	The unique extension name.
publisher	Yes	The name of your publisher, for example: NAV Partner, LLC
application	Yes, if base application objects are extended or referenced	The minimal supported version and locale of the base application to extend, for example: `{ "version": "10.0.0.0", "locale": "W1" }`
platform	Yes, if system tables are referenced in the extension	The minimal supported version of the platform symbol package file, for example: "10.0.0.0". See the List of objects in the platform symbol file section below for the list of object symbols contained in the platform symbol package file.
packageCachePath	Yes, if base application is extended or system tables are referenced	The path to the folder where referenced symbol package files are located. The path could either be absolute or relative to the current extension working directory, for example: "../../resources"

Settings in the launch.json file:

Setting	Mandatory	Value
server	Yes, if connecting to an on-premises server	The HTTP URL of your server, for example: http://localhost
serverInstance	Yes, if connecting to an on-premises server	The instance name of your server, for example: NAV
port	No	The port on which the development endpoint is running on the server, default value: 7049
tenant	No	The tenant ID in case the server is configured for multitenancy.
windowsAuthentication	No	Specifies whether Windows or Azure authentication should be used for publishing the extension. Currently only Windows authentication is supported.
startupObjectId	No	The ID of the startup object to launch when you press F5. Currently only objects of type Page are supported.

Thanks & Regards,
Nandesh Gowda

Understanding Objects and Sample Code Snippet Extensions for New Development Environment

2016-12-24T13:18:00.003+05:30

Hi All,

In my last post I discussed on how to setup Azure 30 days free trial subscription and install a New VM for trying out New Development Environment. Below is the link for the same post.

https://nandeshgowda-navblog.blogspot.in/2016/12/developing-extensions-using-new.html

Understanding Objects in Dynamics NAV

All functionality in Dynamics NAV is coded in objects. Table objects define the table schema that holds data, page objects represent the pages seen in the user interface and codeunits contain code for logical calculations and for the application behavior. These objects are stored as code, known as AL code, and are saved in files with the .al file extension.

Note
A single .al file may contain multiple objects.

For Table Object please refer below MSDN Link
https://msdn.microsoft.com/en-us/dynamics-nav/newdev-table-object

For Page Object please refer below MSDN Link
https://msdn.microsoft.com/en-us/dynamics-nav/newdev-page-object

For Codeunit Object please refer below MSDN Link
https://msdn.microsoft.com/en-us/dynamics-nav/newdev-codeunit-object

There are two other special objects which are specifically used for building extensions. Table extension objects and page extension objects are used for defining additive or overriding changes to table or page objects.

For example, an extension for managing a business that sells organic food may define a table extension object for the Item table that contains an additional field Organic and Produced Locally. The Organic and Produced Locally fields aren't usually present in the Item table, but through the table extension these data fields will now be available to store data in and to access from code.

You can then use the page extension object to display the fields that you added to the table object.

Note :
Table and page extension objects can have a name with a maximum length of 30 characters.

1) Table Extension Object :

The table extension object allows you to add additional fields or to change some properties on a table provided by the Dynamics NAV service. In this way, you can add data to the same table and treat it as a single table.

For example, you may wish to create a table extension for a retail winter sports store. In your solution you want to have ShoeSize as an additional field on the customer table. Adding this as an extension allows you to write code for the customer record and also include values for the ShoeSize.

Along with defining other fields, the table extension is where you write trigger code for your additional fields.

Snippet support :
Typing the shortcut ttableext will create the basic layout for a table extension object when using the AL Extension in Visual Studio Code.

Properties:
Using a table extension allows you to overwrite some properties on fields in the base table. The following properties can be changed.

OptionCaptionML
ClosingDates
Description
Width

Table Extension example :

This table extension object extends the Customer table object by adding a field ShoeSize, with ID 70000900 and the data type Integer. It also contains a procedure to check if the ShoeSize field is filled in.

tableextension 70000020 RetailWinterSportsStore extends Customer
{
    fields
    {
        field(70000900;ShoeSize;Integer) 
        {
            trigger OnValidate();
            begin
                if (rec.ShoeSize < 0) then
                begin
                   message('Shoe size not valid: %1', rec.ShoeSize);
                end;                    
            end;
        }
    }

    procedure HasShoeSize() : Boolean;
    begin
        exit(ShoeSize <> 0);
    end;

    trigger OnBeforeInsert();
    begin
        if not HasShoeSize then
            ShoeSize := Random(42);
    end;
}

2) Page Extension Object

The page extension object extends a Dynamics NAV page object and adds or overrides the functionality.

The structure of a page is hierarchical and breaks down into three sections. The first block contains metadata for the overall page; the type of the page and the source table it is showing data from. The next section; the layout, describes the visual parts on the page. The final section details the actions that are published on the page.

In the layout section, you can use the following functions to place page fields and groups on the page. Similarly, in the actions section, you use these functions to place actions in the ribbon.

Function example	Applies to...
`addfirst(General)`	Groups only
`addlast(General)`	Groups only
`addafter(AddressDetails; "Post Code")`	Fields and groups
`addbefore(AddressDetails; "Post Code")`	Fields and groups
`movefirst(General)`	Groups only
`movelast(General)`	Groups only
`moveafter(AddressDetails; "Post Code")`	Fields and groups
`movebefore(AddressDetails; "Post Code")`	Fields and groups

If you want to modify existing fields and groups on a page, you use the modify() function. See the code example below for syntax.

Snippet support :
Typing the shortcut tpageext will create the basic layout for a table object when using the AL Extension in Visual Studio Code.

Page Extension example :
The following page extension object extends the Customer Card page object by adding a field control ShoeSize to the General group on the page. The field control is added as the last control in the group using the addlast function. In the actions area, you can see what the syntax looks like for actions that execute triggers and actions that run objects.

pageextension 70000020 CustomerCardExtension extends "Customer Card"
{
    layout
    {
        addlast(General)
        {
            field("Shoe Size"; ShoeSize)
            {
                CaptionML = ENU='ShoeSize';

                trigger OnValidate();
                begin
                    if ShoeSize < 10 then
                        Error('Feet too small');
                end;
            }
        }

        modify("Address 2")
        {
            CaptionML = ENU='New Address 2';
        }
    }

    actions
    {
        addlast(Creation)
        {
            group(MyActionGroup)
            {
                Action(MyAction1)
                {
                    CaptionML = ENU='Hello!';

                    trigger OnAction();
                    begin
                        Message('My message');
                    end;
                }

                Action(MyAction2)
                {
                    RunObject = codeunit "Activities Mgt.";
                }
            }
        }
    }

   var
        Msg : TextConst ENU='Hello from my method';

    trigger OnOpenPage();
    begin
        Message(Msg);
    end;
}

Thanks & Regards,
Nandesh Gowda

Using the New Dynamics NAV In-Client Designer

2016-12-24T12:50:00.000+05:30

Hi All,

Using the Dynamics NAV In-Client Designer

With the Dynamics NAV in-client designer, you can create extensions using drag-and-drop inside the client. With this preview of the in-client designer, you can:

Enter and exit design mode
Move fields around
Add existing fields
Preview your design (desktop, tablet, and phone preview)
Save the extension for the tenant

Adding a field

The in-client designer is switched on by choosing the design icon in the ribbon top right corner from any page that you want to make modifications to, and then choosing More.

In design mode you modify the current page; you can add existing table fields, move fields around, or remove fields from the page.

Note :
With this preview you can only add existing table fields. Adding pages, groups, parts, and actions is not yet supported.

Use the add field functionality to add a field to the page. You will get a pane to the right where you can see all of the table fields that are available for the specific page.

The table fields displayed are based on the underlying table or tables. The field can have a status of Placed, which means that the field already exists on the page.
A status of Ready means that the field doesn't already exist on the page, and that you can place it.

You can Remove field by clicking on any of the field on the page.

When you modify subpages on a given page, a square is displayed to mark the area that you can move a field within. This is also true for FactBoxes.

Change a FastTab caption by clicking the caption and start writing.

The display type icons let you preview the changes you made on desktop, tablet, and phone clients. This way you can make sure that your design will work on the intended display target(s).
You can flip to display tablet and phone designs in landscape as well.

All the UI changes are stored as Extensions.

Thanks & Regards,
Nandesh Gowda

Developing Extensions Using the New Development Environment Getting Started NAV

2016-12-24T12:45:00.001+05:30

Hi All,

The Microsoft Dynamics NAV ‘Tenerife’ Developer Preview is still evolving with frequent update.

Extensions are a programming model where functionality is defined as an addition to existing objects and defines how they are different or modify the behavior of the solution.

Below link on MSDN section explains how you can develop extensions using the new development environment for Dynamics NAV.

https://msdn.microsoft.com/en-us/dynamics-nav/newdev-dev-overview.

For previous post on Extensions on my blog please refer below links.

https://nandeshgowda-navblog.blogspot.in/2016/11/extending-microsoft-dynamics-nav-using.html

https://nandeshgowda-navblog.blogspot.in/2016/11/developing-extension-package-nav.html

Here we will discuss on how to get started with the new Development Environment.

To get started writing extensions for Dynamics NAV you will need a Dynamics NAV tenant, and Visual Studio Code. Visual Studio Code is a cross platform editor that you will use for coding and debugging.

For the preview, you will download a VM from the Microsoft Azure Gallery which is set up for trying out the new development environment.
Steps :
1) First, you will need an Azure subscription. You can sign up for a free subscription.

2) Go to Microsoft Azure Marketplace and search for Microsoft Dynamics NAV Developer Preview. Then click on Create to create new Virtual Machine.

3) Fill in the various details and create a new virtual machine. It will take 10-15 mins to create the same.

4) Now connect to VM with the Login credentials given while creating VM.

5) If you can't see Visual Studio Shortcut on Desktop, Open C:\Demo folder and run the script called Install New Developer Experience.ps1 and select Run with Powershell.

6) After Installing you can see the Visual Studio Shortcut on Desktop.

7) Now Open the New Visual Studio Code Editor

Thanks & Regards,
Nandesh Gowda

The remote certificate is invalid according to the validation procedure SMTP NAV

2016-12-10T21:40:00.000+05:30

Hi All,

The remote certificate is invalid according to the validation procedure

The above error may come while sending mails through SMTP in NAV.

The reason may be you have setup Secured Connection in SMTP setup in NAV, while the SMTP Server doesn't have valid certificate to accept the secure connection.

You can install a valid certificate on Server or you can untick Secured Connection in SMTP setup to connect with unsecured connection.

Thanks & Regards,
Nandesh Gowda

There is a Communication protocol mismatch between the client and the server for NAV 2013 R2

2016-12-10T21:36:00.000+05:30

Hi All,

There is a Communication protocol mismatch between the client and the server.

You may get above error while connecting to NAV RTC Client in NAV 2013 or NAV 2013 R2.

The error is due to the mismatch of Configuration Settings between ClientUserSettings.config file on Client with the NAV Server Instance Configuration Settings.

For Ex : ClientServicesCredentialType is set to NavUserPassword on ClientUserSettings.config

and the Credential Type set on NAV Server Instance is Windows.

Thanks & Regards,
Nandesh Gowda

To add a Microsoft Dynamics NAV web server instance

2016-12-10T21:35:00.000+05:30

Hi All,

To add a Microsoft Dynamics NAV web server instance

1) On the computer or virtual machine that is running Microsoft Dynamics NAV Server, run Microsoft Dynamics NAV Administration Shell as an Administrator.

Choose Start, in the Search box, type Microsoft Dynamics NAV Administration Shell.

Right-click the related link, and then choose Run as Administrator.

2) At the command prompt, type the following command:

New-NAVWebServerInstance -WebServerInstance -Server -ServerInstance -ClientServicesCredentialType

Specifies the name that you want to give the Microsoft Dynamics NAV Web client application instance. This name will become part of the URL for the Microsoft Dynamics NAV Web client application, for example, http://MyWebServer:8080/MyWebApp/WebClient.

Specifies the name of the computer that is running the Microsoft Dynamics NAV Server to connect the Microsoft Dynamics NAV web server to.

Specifies the name of the Microsoft Dynamics NAV Server instance to connect the web server instance to.

Specifies the credential type that is configured for the Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Server. Valid options are NavUserPassword, Windows, UserName, and AccessControlService. The default value is NavUserPassword.

Note :

The command that is shown includes only the required parameters of the NAVWebServerInstance cmdlet. The cmdlet has several other parameters that can be used to configure the web server instance.

3.Press Enter to run the cmdlet.

A new Microsoft Dynamics NAV web server instance with the specified name is added to the Microsoft Dynamics NAV Web client site on IIS

If you want to change the configuration of the new Microsoft Dynamics NAV web server instance after it has been added, modify the web.config file.

For more information, see Configuring Microsoft Dynamics NAV Web Client by Modifying the Web.config File.

Thanks & Regards,
Nandesh Gowda

A fatal error occurred. The connection to SQL server cannot be established NAV

2016-12-10T21:34:00.000+05:30

Hi All,

When you try to open Microsoft Dynamics NAV Web client, you get the following error:

A fatal error occurred. The connection to SQL server cannot be established or is no longer usable.

There can be various causes of this error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL Server is not configured correctly.

Resolution :

1) Microsoft Dynamics NAV Server connects to the correct database by using the correct login account. You can verify this by using the Microsoft Dynamics NAV Server Administration tool.

2) Login account has the following permissions:

Permission to log on as a service on the computer that is running SQL Server. For more information, see Provisioning the Microsoft Dynamics NAV Server Account.

Set up as a user in the Microsoft Dynamics NAV database on SQL Server with the following role memberships: db_datareader, db_datawriter, and db_ddladmin.

3) SQL Server has the following configurations:

TCP/IP protocol is enabled.

SQL Server executable file is allowed through the Windows Firewall.

SQL Server Browser Service is running. This is required only when Microsoft Dynamics NAV used a named database instance, such as NAVDEMO, and Microsoft Dynamics NAV Server is on a different computer than SQL Server.

For more information, see Troubleshooting: SQL Server Connection Problems.

Thanks & Regards,
Nandesh Gowda

A server error occurred and the content cannot be displayed NAV Web Client

2016-12-10T21:33:00.000+05:30

Hi All,

When you try to open the Microsoft Dynamics NAV Web client, you get the following error:

A server error occurred, and the content cannot be displayed. Refresh the page or open a new browser window.

In the Event Viewer of the computer that is running Microsoft Dynamics NAV Web Server components, the Windows application log includes the following event:

Message: A server was not found at “net.tcp://navserver:7046/DynamicsNAV71/Service”. Either the URL is incorrect or the server is currently not available.

This error occurs when the Microsoft Dynamics NAV Web client cannot connect to Microsoft Dynamics NAV Server.

To resolve this error, verify that the following conditions are met:

• The Microsoft Dynamics NAV Web client is configured to connect to the correct Microsoft Dynamics NAV Server. Also please check the Server Instance, Port No.,Credential Type,etc and other configuration settings in Web.Config File.

• The logon account of Microsoft Dynamics NAV Server has permission to log on as a service on the computer that is running Microsoft Dynamics NAV Server.

• If you are using Mozilla Firefox as your browser, then you must enable cookies in the browser. Additionally, configure the address of the Microsoft Dynamics NAV Web client as a trusted URI in Firefox. For more information, see How to: Configure Mozilla Firefox for Microsoft Dynamics NAV Clients.

• If IIS and the Microsoft Dynamics NAV Server are on separate computers, verify the following conditions:

1) If the Microsoft Dynamics NAV Web client is using Windows authentication, then the Negotiate provider must be included at the top of the providers list in the Windows authentication setup in IIS. For more information, see Configuring the Credential Type on the Microsoft Dynamics NAV Web Client Website.

2) Delegation is configured from the computer that is running IIS to the computer that is running Microsoft Dynamics NAV Server, including the following:

Kernel mode authentication is either disabled or configured to use the service account of Microsoft Dynamics NAV Server (Microsoft Dynamics NAV Web client only).

The following Service Principal Names are registered for the logon account of Microsoft Dynamics NAV Server:

DynamicsNAV/navserver:port

DynamicsNAV/navserver.domain:port

If you still get this error after verifying the setup, then disable the Use Kerberos Only option in the delegation setup and try again. The Use Kerberos Only option does not work on some network configurations with Microsoft Dynamics NAV.

Thanks & Regards,
Nandesh Gowda

Developing Extension package NAV

2016-11-16T20:44:00.000+05:30

Hi All,

Please refer my previous post on Extensions Overview.
https://nandeshgowda-navblog.blogspot.in/2016/11/extending-microsoft-dynamics-nav-using.html

Today we will discuss on how to develop & use Extensions.

We can build extension packages that add functionality to a Dynamics NAV deployment. Unlike the familiar development and deployment of Dynamics NAV functionality, building an extension relies on the exported version of an application to .TXT files.

We can export the application from the development environment, use the development environment commands, or use the Windows PowerShell cmdlet that is available in the Microsoft Dynamics NAV 2017 Development Shell, Export-NAVApplicationObjectLanguage.

I will create a new field on Customer table and put some validation on that field using Events.

Please refer my below post on how to implement Events
https://nandeshgowda-navblog.blogspot.in/2016/09/implementing-events-in-nav-2016.html

1) To start with please create a folder structure similar to below so that while creating a extension package we can use below path for Cmdlets for converting/merging and creating delta.

2) The foundation for our extension is the exported .txt files of the objects we are modifying. We can export just the objects that we want to modify, or we can export the entire Dynamics NAV application. We can use Export-NAVApplicationObjectLanguage cmdlet to export the objects.

3) Now we need to create a functionality using Events, In my example I have just added a field in Customer table and added a validation on onBeforeValidateEvent of new field created. I have used Events for the code changes.

4) Write extension upgrade code for new or modified tables. This is needed as we may get error while building the Extensions. For time being you can just create upgrade codeunit and add the functions in it.

To write upgrade code for an extension

Create new codeunit.

Important

This must be a codeunit of type Normal, not an Upgrade codeunit.

Add upgrade functions to the codeunit. Make sure the function is declared as global so that the Local property is set to No.

Add the OnNavAppUpgradePerDatabase() function if the extension contains cross-company tables.

Add the OnNavAppUpgradePerCompany() function if the extension contains per-company tables.

5) Now I will verify whether the changes are working from RTC Client.

6) Now Export the Modified objects in text format.

7) Our delta files must be one-to-one with the objects we have added or modified.

We cannot include a single merged delta file. If we output our export file as a single file use the Split-NAVAppplicationObjectFile cmdlet to create the individual files.

Go to "Microsoft Dynamics NAV 2017 Development Shell" and type the command to split the file into individual objects

8) Create DELTA files using the Microsoft Dynamics NAV 2017 Development Shell cmdlets.

Extension packages are based on application object deltas. Again, we use the application merge utilities in the Microsoft Dynamics NAV 2017 Development Shell to distill the changes in the form of application object differences that are stored in DELTA files.

We use the Compare-NAVApplicationObject cmdlet to create these delta files.

If we will be adding Multilanguage translations for captions or constant. Use below cmdlet.

Compare-NAVAppApplicationObjectLanguage -OriginalPath MLORIGINAL -ModifiedPath MLMODIFIED -DeltaPath MLDELTA

9) Build Extension package.

Use the New-NAVAppManifest and New-NAVAppPackage cmdlets to build the manifest and package file.

The following is an example of how to create a new extension .NAVX package file with a new manifest.

10) Signing a NAVxfile.

Code signing is a common practice for many applications. We must have a certificate on the computer (as a file or in the certificate store) that includes code signing for the intended purpose.

It is recommended that we use a certificate from a third party certificate authority. For testing purposes, it is acceptable to create a self-signed certificate using the New-SelfSignedCertificate cmdlet in PowerShell on Windows 10 or MakeCert.

I will Skip this process of Signing in this Demo. We will use unsigned extension package to Publish and Install.

11) Publish and Install extension :

We have packaged our extension so it is ready to be published and installed on a target server.

Please take a new & clean database without any customisations done to publish and install the extensions.

Use Publish-NAVApp cmdlet to publish the Extension for the service Instance

To Install we can use Install-NAVApp cmdlet

Install-NAVApp -ServerInstance YourDynamicsNAVServer -Name ”My Extension” –Tenant Tenant1, Tenant3

OR

We can install the same from RTC NAV Client

Go to Extension Management and install the published extension in our case FOCCustomer.

Now after installing we can verify whether our changes are reflecting on customer card.

NOTES :

1) Objects must be exported as .TXT files. We cannot build an extension based on a .FOB file.

2) DO NOT make C/AL code modifications.

3) DO use subscribing to events to execute code.

4) DO NOT change restricted page and table properties.

5) The packaging process adds a description of the extension to the manifest, such as whether it changes pages or adds tables. While not explicitly being enforced currently, this can be used to determine whether to install an extension, or not.

6) If we want to publish an unsigned extension package, we need explicitly state that by using the –SkipVerification parameter on the Publish-NAVApp cmdlet.

7) When we install an extension that includes changes to the menu suites, this does not take effect for any user until we sign out and then sign in again.

Please refer below MSDN links for Extensions

1) Developing Extensions for NAV 2017
https://msdn.microsoft.com/en-us/dynamics-nav/how-to--develop-an-extension

2) Create an Extension package for NAV 2017
https://msdn.microsoft.com/en-us/dynamics-nav/how-to--create-an-extension-package

3) Publish and Install Extension for NAV 2017
https://msdn.microsoft.com/en-us/dynamics-nav/how-to--publish-and-install-an-extension

4) How to Write Extension Upgrade Code for NAV 2017
https://msdn.microsoft.com/en-us/dynamics-nav/extensions-upgrade-howto

5) Extension Packages Capability Support Matrix for NAV 2017
https://msdn.microsoft.com/en-us/dynamics-nav/extension-packages-capability-support-matrix

Thanks & Regards,
Nandesh Gowda

Extending Microsoft Dynamics NAV Using Extension Packages

2016-11-16T20:41:00.002+05:30

Hi All,

You can extend and customize a Dynamics NAV deployment without modifying the original application objects. With extension packages, you install, upgrade, and uninstall functionality in on-premises deployments or for select tenants in a multitenant deployment. Customers can easily add or remove horizontal or customized functionality to their solution that upgrade much easier than past solutions.

The main difference from classical development is that source code modifications are not allowed. Instead, you use C/AL events to extend and customize objects.

Extensions are delivered as .navx package files. A .navx package contains the various artifacts that deliver the new functionality to the Dynamics NAV deployment as well as a manifest that specifies the name, publisher, version, and other attributes of the extension. You manage .navx packages with a series of Windows PowerShell cmdlets that are available in the Microsoft Dynamics NAV 2017 Administration Shell. There are also cmdlets available to ISVs and developers in the Microsoft Dynamics NAV 2017 Development Shell that help create packages.

How Extensions Work

Extensions are in the simplest terms the runtime application of objects and object deltas for a specific combination of an extension package and a tenant. When an extension is published to a Dynamics NAV deployment, it compiles the objects in it against the current application database. Then, when the extension installs for a tenant, it stores the association and builds the relevant database schema. At runtime, Dynamics NAV simply loads the associated objects for that extension and tenant.

You can publish multiple extensions to a Dynamics NAV deployment and, in multitenant deployments, install any combination of published extensions for each tenant. For example, consider a scenario with a multitenant deployment with extensions A, B, C, and D published to it. Each tenant can have their own unique combination of extensions. So tenants 2, 3, and 4 can have the same extensions (extensions B and C) while tenants 1 and 5 only have one extension each, extension A and D, respectively. This provides for a great degree of customer functionality choice while at the same time maximizes the server hardware and administration workload.

In most cases, two extension packages can coexist and work independently of each other; however there is the possibility that two apps will try to modify the same object properties. In those cases, if the conflict cannot be resolved, the installation of the conflicting extension fails.

You can refer below MSDN Link for detailed explanation about Extensions.

https://msdn.microsoft.com/en-us/dynamics-nav/extending-microsoft-dynamics-nav-using-extension-packages

As per my understanding we will have a dilemma whether to go for extensions or use the traditional development methods.

We can have below consideration while choosing Extensions :

1) Is the database going to be heavily customized or not?

2) Is the development done can be easily maintained and monitored?

3) How frequently the changes will come in your existing extensions ?

4) What level of IT hardware & Configuration needed for extension?

5) More the extensions used, more consideration to be given for Server hardware configuration as the extensions will be loaded by NAV at run time.

6) Upgrade Flexibility

7) Multi Tenant Environment Flexibility

8) Using extensions for third party App, ISV, etc.

Anyways we need to move forward and start using Extension packages for most of our developments.
.
I feel in future Extensions will be heavily concentrated on and improvements will come in this regard. As its obvious from NAV 2016 and NAV 2017 releases and changes w.r.t to Extensions.

Thanks & Regards,
Nandesh Gowda

Cannot add the Field Trigger or cannot add variable NAV Extensions

2016-11-16T20:41:00.001+05:30

Hi All,

Cannot add the Field Trigger to.

Above error may come when creating Extension package using New-NAVAppPackage cmdlet.

The above error may come if you have written some code on Triggers of page or table for a field.

So please remove the code and use the Events to implement your code.

We have default trigger events available for table or page to write our code on when you subscribe to table/page object.

Cannot add variable to

Again this is similar kind of error, please remove the variable defined from the object and implement the logic using Events.

Thanks & Regards,
Nandesh Gowda