Generic NAV 2016 Extension

Tags:

Updated:

8 minute read

Here you will get the step by step process to use NAV 2016 Extension as and when required in the data integration business scenario.

ProTip: Before installation of INS2.01 Extension please keep a backup of the NAV Database.

Installation of INS2.01 Extension for NAV2016

Installation of INS2.01 has been divided into two tasks as given below :

1. Importing of .fob files and web services XML file

2. Manual changes in base pages

Importing of .fob files and web services XML file

1) You need to import below listed .fob files

  • table
  • page
  • codeunit
  • xmlport

2) There is two option to import extension WebServices from XML file and they are provided below :

a) Run AEC WebServices Import xmlport. An import popup will appear. Specify a direction value import and click OK button. Another popup will be shown where you need to select the Webservices of the XML file.

b) Run the ins import codeunit where we have called AEC WebServiceImport function with a parameter datafilepath. This datafilepath is webservices of XML file path. You will be provided with XML file in extension build. You need to change the function parameter path value as per your webservice XML file location. This will insert data in Dynamics NAV Web Service table.

Manual changes in Base Pages

We have added some base table fields and the extension page in base Page.

NOTE : After inserting the 1st part in each of the base pages you need to click on the right shift-arrow to make it distinguishable from the previous group. (#Left shift is done to keep the child separately as a field within the group and not as any sub-child of a child)

manualchange-basepage1

Changes in Customer Card Page

a) We have added our Extension page AEC Customer Page (33064472) as a part type with the name WebCustomer Details. After the creation of the WebCustomerDetails, click on the property button. The WebCustomerDetails property window opens. In this window, PagePartID as AEC Customer Page, SubpageLink field as No. and base page SubPageLink field as No. has been added.

customercard-page-nav2016

Child Link Page Details

ID Name Type SubType
33064472 WebCustomer Details Part Page

The property value should be set

Property Value
SubPageLink No=FIELD(No.)
PartType Page
PagePartID AEC Customer Page

b) We have added our Extension page AEC Application Customer List (33064474) as a part type with the name AEC Application Customer List. Click on Property button and Application Customer Detail page appears. In this window, PagePartID as AEC Application Customer List, SubPage Link field as CustomerNo and base page SubPageLink field as No. has been added.

aecapplication-customerlist-nav2016

Child Link Page Details

ID Name Type SubType
33064474 AEC Application Customer List Part Page

The property value should be set

Property Value
SubPageLink CustomerNo=FIELD(No.)
PartType Page
PagePartID AEC Application Customer List

Note : In NAV 2017 the same changes will be applicable as mentioned in A.(a),(b) above “Container” type.

customercard-nav2016

Note : There is a slight change in the Page View in NAV 2017 as two additional fields are now visible just below which you will have to make the necessary changes.

Changes in Item Card Page

a) We have added our Extension page Web Product Details Page (33064469) as a part type with name WebProductDetails. Click on Property button and Web Product Details window appears. In this window, PagePartID as Web Product Details Page, SubPageLink field as ItemNo. and base page SubPageLink field as No. has been added.

itemcard-nav2016

Child Link Page Details

ID Name Type SubType
33064469 WebProductDetails Part Page

The property value should be set

Property Value
SubPageLink ItemNo=FIELD(No.)
PartType Page
PagePartID Web Product Details CP Page

b) We have added our Extension page Web ProductWebsites Page (33064466) as a part type with name ProductWebSites. Click on Property button and the ProductWebSites window appears. In this window, PagePartID as Web ProductWebsites Page, SubPageLink field as ItemNo. and base page SubPageLink field as No. has been added.

webproduct-websitepage-nav2016

Child Link Page Details

ID Name Type SubType
33064466 ProductWebSites Part Page

The property value should be set

Property Value
SubPageLink ItemNo=FIELD(No.)
PartType Page
PagePartID Web ProductWebsites Page

c) We have added our Extension page Web ProductAttribute Page (33064467) as a part type with name ProductAttributes. Click on Property button and the ProductAttributes window appears. In this window, PagePartID as Web ProductAttribute Page, SubPageLink field as ItemNo and base page SubPageLink field as No. has been added.

webproduct-attributepage-nav2016

Child Link Page Details

ID Name Type SubType
33064467 ProductAttributes Part Page

The property value should be set

Property Value
SubPageLink ItemNo=FIELD(No.)
PartType Page
PagePartID Web ProductAttribute Page

d) We have added our Extension page Web ProductCategory Page (33064468) as a part type with name ProductCategories. Click on Property button and the ProductCategory window appears. In ProductCategory Page, PagePartID as Web ProductCategory Page, SubPageLink field as ItemNo and base page SubPageLink field as No. has been added.

webproduct-categorypage-nav2016

Child Link Page Details

ID Name Type SubType
33064468 ProductCategories Part Page

The property value should be set

Property Value
SubPageLink ItemNo=FIELD(No.)
PartType Page
PagePartID Web ProductCategory Page

e) We have added our Extension page Web Product Child Details (33064471) as a part type with name ProductChild. Click on Property button and the Product Child window appears. In Web Product Child Page, PagePartID as Web Product Child Details, SubPageLink field is ItemNo and base page SubPageLink field is No. has been added.

webproduct-childdetails-nav2016

Child Link Page Details

ID Name Type SubType
33064471 ProductChild Part Page

The property value should be set

Property Value
SubPageLink ParentItemNo=FIELD(No.)
PartType Page
PagePartID Web Product Child Details

f) We have added our Extension page AEC Application Item List (33064475) as a part type with the name ProductApplicationData. Click on Property button and the Product application data window appears. In AEC Application Item List window, PagePartID as AEC Application Item List, SubPageLink field as ItemNo and base page SubPageLink field as No. has been added.

aec-application-itemlist-nav2016

Child Link Page Details

ID Name Type SubType
33064475 ProductApplicationData Part Page

The property value should be set

Property Value
SubPageLink ParentItemNo=FIELD(No.)
PartType Page
PagePartID AEC Application Item List

Changes in Sales Order Page

a) We have added our Extension page AEC Order Header Details (33064476) as a part type with name WebOrder Header Details. Click on Property button and the WebOrder header details window appears. In this window, PagePartID as AEC Order Header Details, SubPageLink field as OrderNo and base page SubPageLink field as No. has been added.

sales-orderpage-nav2016

Child Link Page Details

ID Name Type SubType
33064476 WebOrder Header Details Part Page

The property value should be set

Property Value
SubPageLink OrderNo=FIELD(No.)
PartType Page
PagePartID AEC Order Header Details

b) We have added our Extension page AEC Order Line Details (33064477) as a part type with name WebOrder Line Details. Click on Property button and the WebOrder Line details window appears. In this window, PagePartID as AEC Order Line Details, SubPageLink field as OrderNo and base page SubPageLink field as No.` has been added.

orderline-detailspage-nav2016

ID Name Type SubType
33064477 WebOrder Line Details Part Page

The property value should be set

Property Value
SubPageLink OrderNo=FIELD(No.)
PartType Page
PagePartID AEC Order Line Details

Changes in Ship-to Address Page

a) We have added our Extension page AEC Ship-To Address Cart Part (33064478) as a part type with name WebDetails. Click on Property button and the webdetail window appears. In this window, PagePartID as AEC Ship-To Address, SubPageLink field as CustomerNo and Code and base page SubPageLink field as CustomerNo and Code has been added.

ship-to-addresspage-nav2016

ID Name Type SubType
33064478 WebDetails Part Page

The property value should be set

Property Value
SubPageLink CustomerNo=FIELD(Customer No.),Code=FIELD(Code)
PartType Page
PagePartID AEC Ship-To Address CartPart

Add a base table (Ship-to Address) field “Customer No.” with name “Customer_No”.

ship-to-addresspage2-nav2016

Name SourceExp Type
Customer_No. Customer No. Field

Note : In NAV 2017, you do not need to Add a base table (Ship-to Address) field “Customer No.” with the name “Customer_No, since it has already been provided. You only need to do the same changes as defined in step a.

ship-to-addresspage3-nav2016

ship-to-addresspage4-nav2016

Changes in Contact Card Page

a) We have added our Extension page AEC Contact Details CardPart (33064481) as a part type with name AEC Contact Details CardPart. Click on Property button and the AEC Contact Details CardPart window appears. In this window, SubPageLink field as No and base page SubPageLink field as No.

contact-card-nav2016

ID Name Type SubType
33064481 AEC Contact Details CardPart Part Page

The property value should be set

Property Value
SubPageLink No=FIELD(No.)
PartType Page
PagePartID AEC Contact Details CardPart

b) We have added our Extension page AEC Application Contact LP (33064482) as a part type with the name AEC Application Contact List. Click on Property button and the AEC Application Contact List window appears. In this window, PagePartID as AEC Application Contact LP, SubPageLink field as CustomerNo and base page SubPageLink field as No.

contactLP-nav2016

ID Name Type SubType
33064482 AEC Application Contact List Part Page

The property value should be set

Property Value
SubPageLink ContactNo=FIELD(No.)
PartType Page
PagePartID AEC Application Contact LP

Changes in Contact Alt. Address Card Page

a) We have added our Extension page AEC Contact Address CardPart (33064483) as a part type with the name AEC Contact Address CardPart. Click on Property button and the AEC Contact Address CardPart window appears. In this window, PagePartID as AEC Contact Address CardPart, SubPageLink field as ContactNo and Code and base page SubPageLink field as Contact No. and Code.

contact-alt-addresscard-page-nav2016

ID Name Type SubType
33064483 AEC Contact Address CardPart Part Page

The property value should be set

Property Value
SubPageLink ContactNo=FIELD(Contact No.), Code=FIELD(Code)
PartType Page
PagePartID AEC Contact Address CardPart

b) Add a base table (Contact Alt. Address) field Contact No. with the name Contact_No.

manualchange-contactalt2

Name SourceExpr Type
Contact_No Contact No. Field

Managing Variants in AEC Extension

managingvariants-extension

In the Above Screen, if the Checkbox for “MaintainCrossReference” is enabled, the users can add the variants from the table “ItemCrossReference” for sync purpose as enabling this field populates the data from the table “ItemCrossReference” to “WebProductChildDetails”. And if the checkbox for “MaintainCrossReference” is disabled, the Variants will be added from the table “Item Variants” to “WebProductChildDetails”.

Note: This is done only for Dynamics NAV 2016.

Troubleshoot

Before installing the extension you always need to keep a backup of your existing database, as installation and uninstallation of extension may happen multiple times.