User Tools

Site Tools


Sidebar

Back to Main Website

Video Tutorials

User Guide

1. General Information

2. Starting Up

3. Connecting data

4. Demand and Sales Forecasting

5. Inventory Planning

6. Reference

nav-connection-guide

3.5.2. How to Import Data from Dynamics NAV

In order to import data using this guide, you need a NAV developer license and Microsoft Dynamics NAV 2013 or higher. If you do not have such a license or have an older NAV version, you can import the data using SQL-queries via the Database connection. Here are examples of the queries to a NAV database: transactions.sql, items.sql, in-transition.sql.

Streamline establishes a web connection in order to import data from NAV.

Open the Dynamics NAV connection dialog by clicking menu File > New > Dynamics NAV connection.

In the Authentication section, fill in the credentials of your Windows account that has permissions to start NAV.

In the URLs section you should set up four NAV web-services’ URLs which provide information about:

  • sales and purchase transactions (Transactions service),
  • products (Item info service),
  • products being in transition (In transition service),

and create purchase orders in NAV (Create Purchase Orders service). Description of how to create the web-services is given below.

The Settings section allows you to aggregate imported data by a given period and limit the import by using the starting from parameter.

Creating NAV web services

The first three services read data from NAV and the last one (Creating Purchase Orders) – writes them into NAV. Each read-service returns a result of SQL queries which data are read by the application. To import data into Streamline, the connector uses the Database connection functionality. Thus, the data that can be imported using these services are limited by the Database connection capabilities.

Let’s consider creating a read-service.

Creating a read-service

To create a read-service we need to:

  1. Create a view that will return the result of the query.
  2. Create a NAV table that will contain the result of the query.
  3. Create a NAV page that will display the table.
  4. Publish the page as a web-service.

Let’s consider creating the In transition service. Other services can be created using the same actions. To demonstrate it, we will use the CRONUS Company demo database, shipped with NAV.

1 Creating a view

First, we need to create a SQL view that returns a table having Item code, Location, Arrival Date and Quantity columns. To do this, open SQL Server Management Studio and create a new query by clicking menu File > New > Query with Current Connection. Paste the following code in the newly created query-file:

USE [NAVDEMO]
GO
 
CREATE VIEW [dbo].[CRONUS International Ltd_$In Transition] AS
SELECT			
	i.No_ AS [Item Code],		
	'' AS Location,
	l.[Expected Receipt Date] AS [Arrival Date],		
	l.Quantity	
FROM dbo.[CRONUS International Ltd_$Purchase Line] l
INNER JOIN dbo.[CRONUS International Ltd_$Purchase Header] h
  ON h.[No_] = l.[Document No_]
INNER JOIN dbo.[CRONUS International Ltd_$Item] i
  ON l.No_ = i.No_
WHERE l.Quantity > 0 
  AND l.[Quantity Received] = 0
  AND l.Type = 2
  AND h.[Document Type] = 1 
GO

After clicking menu Query > Execute, you should see the newly created view under the Views in the Object Explorer tree (see fig. below). If it does not appear, select the Views and click menu View > Refresh.

2 Creating a table

Now, we need to create a NAV table that will be attached to the In Transition view. Open Dynamics Development Environment and click File > Database > Open. In the Open Database dialog, enter the server and database name, and set authentication to Windows Authentication. Click OK.

Click menu Tools > Object Designer. On the left side of the window, select the Table category and click the New button.

Now, we need to declare columns of the new table with exactly the same names and compatible datatypes as the fields in the In Transition view.

After that set the cursor on the next empty field and click menu View > Properties. In the Table Properties window set the LinkedObject property to Yes. This will link our In Transition view to this table.

Close the window and close the Table Designer window. NAV will prompt you to save the changes, click Yes. The Save As dialog asks you to enter table ID and Name. According to the NAV documentation, the user-defined ID range is [50,000-99,999], so we can choose any unused value. The Name must be the same as the In Transition view name, in our case, “In Transition”.

Click OK. Now the In Transition table will appear in the list.

To test it, click the Run button. This will launch the Dynamics NAV Client and shows the result in a separate window.

3 Creating a page

NAV allows publishing a Page, Query or CodeUnit object as a web-service. . In our case Pages will be used to expose the In Transition and Item Info read-services and a Query – to expose the Transactions service. So let’s create a page that will display the In Transition table.

Select the Page category in the Object Designer window and click the New button. In the Table field enter the table name you want to show on the new page. In our case, this is the In Transition table. Click Create a page using a wizard option and select List from the choices. Click OK.

Add all the fields on the page and click the Finish button. Close the Page Designer dialog, and click Yes to save the changes. Enter page ID (choose any unused id from the range described above). Type a name for the page and click OK in the Save As dialog.

After that, the In Transition page will appear in the list.

4 Publishing a web-service

Finally, let’s publish the created page as a web-service.

Run the NAV Client, go to Departments > Administration > IT Administration > General. Click on the Web Services link in the Lists section.

Click the New button in the toolbar. In the New – Web Services window, set the cursor on the first empty line. Choose Page in the Object Type column, type the page ID in the Object ID column (in our case ‘50002’). Enter the service name in the Service Name column (this name will be a part of the web-service URL). Publish the service by selecting the Published check box.

To test the web-service, select it and its link in the OData URL column. The URL will be opened in the default browser. The result should be similar to:

<?xml version="1.0" encoding="utf-8"?>
<feed xml:base="http://localhost:7048/DynamicsNAV80/OData/"
  xmlns="http://www.w3.org/2005/Atom"
  xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices"
  xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
  <id>http://localhost:7048/DynamicsNAV80/OData/Company('CRONUS%20International%20Ltd.')/InTransition</id>
  <title type="text">InTransition</title>
  <updated>2016-11-08T15:50:03Z</updated>
  <link rel="self" title="InTransition" href="InTransition" />
  <entry m:etag="W/&quot;'32%3BUsMAAAF7MQA4ADkANgAtAFMAAAAAAA%3D%3D1%3B00%3B'&quot;">
    <id>http://localhost:7048/DynamicsNAV80/OData/Company('CRONUS%20International%20Ltd.')/InTransition('1896-S')</id>
    <category term="NAV.InTransition" scheme="http://schemas.microsoft.com/ado/2007/08/dataservices/scheme" />
    <link rel="edit" title="InTransition" href="Company('CRONUS%20International%20Ltd.')/InTransition('1896-S')" />
    <title />
    <updated>2016-11-08T15:50:03Z</updated>
    <author>
      <name />
    </author>
    <content type="application/xml">
      <m:properties>
        <d:Item_Code>1896-S</d:Item_Code>
        <d:Location></d:Location>
        <d:Arrival_Date m:type="Edm.DateTime">2016-01-06T00:00:00</d:Arrival_Date>
        <d:Quantity m:type="Edm.Decimal">100</d:Quantity>
        <d:ETag>32;UsMAAAF7MQA4ADkANgAtAFMAAAAAAA==1;00;</d:ETag>
      </m:properties>
    </content>
  </entry>
  <entry m:etag="W/&quot;'32%3BUsMAAAF7MQA5ADAANgAtAFMAAAAAAA%3D%3D1%3B00%3B'&quot;">
    <id>http://localhost:7048/DynamicsNAV80/OData/Company('CRONUS%20International%20Ltd.')/InTransition('1906-S')</id>
    <category term="NAV.InTransition" scheme="http://schemas.microsoft.com/ado/2007/08/dataservices/scheme" />
    <link rel="edit" title="InTransition" href="Company('CRONUS%20International%20Ltd.')/InTransition('1906-S')" />
    <title />
    <updated>2016-11-08T15:50:03Z</updated>
    <author>
      <name />
    </author>
    <content type="application/xml">
      <m:properties>
        <d:Item_Code>1906-S</d:Item_Code>
        <d:Location></d:Location>
        <d:Arrival_Date m:type="Edm.DateTime">2016-02-03T00:00:00</d:Arrival_Date>
        <d:Quantity m:type="Edm.Decimal">50</d:Quantity>
        <d:ETag>32;UsMAAAF7MQA5ADAANgAtAFMAAAAAAA==1;00;</d:ETag>
      </m:properties>
    </content>
  </entry>

Click OK to close the New – Web Services window.

The URL for the In Transition field of the Dynamics NAV connection dialog in our example is: http://localhost:7048/DynamicsNAV80/OData/Company('CRONUS%20International%20Ltd.')/InTransition

Generally, you will need to replace localhost with the IP of the machine running the NAV Server.

5 Setting the meaning of read-service table columns

In order to understand read-service data correctly by Streamline, we need to set up the proper column type for each of the table columns returned by a service. To do this, click on the Preview button near the read-service link of the NAV connection dialog. The result of the query will appear in the table below.

Click on the combo-box under each column header and choose the most appropriate type in the drop-down list.

Repeat steps 1-5 for the Items and In transition services. You can download SQL queries for all the read-services: transactions.sql, items.sql, in-transition.sql.

For the Transactions service the third step is creating a Query instead of creating a Page (explained below).

Creating a query

Streamline requires that Transactions service returns records ordered by date. Therefore we will create a query that orders the Transactions table by date and then publish it as a web-service.

Go to the Query category in the Object Designer window and click the New button. Leave the Type as it is by default (DataItem). In the Data source column click on the arrow and choose the Transactions table in the appeared list. Now, let’s add all the columns of the table in the query. To do this, set the cursor on the next line (the Type will be set to ‘Column’ automatically) and click the arrow in Data Source column. Choose one of the table fields. Repeat this procedure until all the fields are added to the query.

To open the query properties, set the cursor on the last line of the Query dialog and go to menu View > Properties. We need here to set the OrderBy property. Click on the button on the right of the Value column. Set the Direction to descending order of the Order by dialog. Then click on the arrow in the Column. Choose the Date field in the list.

Click OK to close the Order By dialog. Close the Query Properties dialog. Close the New Query dialog. Enter an ID from the user range and a name, for example, ‘Transactions’ and save the query.

Now this query will appear in the list. To test it, select it and press the Run button. The Transactions table ordered by date will be opened in a separate window.

The link for the Transactions service in the Dynamics NAV connection dialog must also contain the orderby parameter: "http://localhost:7048/DynamicsNAV80/OData/Company('CRONUS%20International%20Ltd.')/SalesHistory?&$orderby=Date desc"

Creating the write-service

Now, let’s make up a web-service that creates purchase orders in NAV. We need to create two functions: the first creates an order by the given vendor code and returns its number, the second adds a purchase line into the purchase order using the given order number. A purchase line is described by item code and item quantity.

To do this, we will use NAV Codeunits. So, open NAV Development Environment, select Codeunit in the left menu and click the New button.

First, we need to declare these functions in the codeunit. To do this, click the menu View > C/AL Globals. Click on the Functions tab of the C/AL Globals window. Let’s name them createPurchaseOrder and createPurchaseLine. Enter these names into the list.

Set the cursor on the line with the function name, click menu View > Properties and set Local property to No.

Now, let’s specify the declaration of the functions by adding their input and output parameters. Set the cursor on the line with the createPurchaseOrder function, and click on the Locals button.

The input parameters are declared on the Parameters tab. Let’s add a parameter named VendorNo. Its DataType is Code.

The return value of the function will be OrderNo with data type Code also.

In the body of the function, we will use a local variable that is linked to the record of the NAV PurchaseHeader table. Function’s local variables are declared on the Variables tab. Add a variable named PurchaseHeader with DataType of Record. To set the Subtype, click on the arrow in the right corner of the field and choose the 38th line which is Purchase Header.

Do the same actions for the createPurchaseLine using the information from the table below.

Name DataType Subtype Length
Input variables
OrderNo Code 10
ItemNo Code 20
Quantity Integer
Local variables
PurchaseLine Record Purchase Line
PurchaseHeader Record Purchase Header
NextLineNo Integer

After completing all of this, you should have the following functions’ declarations in the C/AL Editor window:

Now, let’s write the functions’ bodies. Set the cursor on the next empty line after the declaration of the createPurchaseOrder function and copy-paste the following code:

PurchaseHeader.INIT;
PurchaseHeader.VALIDATE("Document Type",PurchaseHeader."Document Type"::Order);
PurchaseHeader.VALIDATE("Buy-from Vendor No.",VendorNo);
PurchaseHeader.INSERT(TRUE);
EXIT(PurchaseHeader."No.");

Add the following body for the createPurchaseLine function:

PurchaseLine.RESET;
PurchaseLine.SETRANGE("Document Type",PurchaseHeader."Document Type"::Order);
PurchaseLine.SETRANGE("Document No.",OrderNo);
IF PurchaseLine.FIND('+') THEN
  NextLineNo := PurchaseLine."Line No." + 10000
ELSE
  NextLineNo := 10000;
IF NextLineNo = 10000 THEN

CLEAR(PurchaseLine);
PurchaseLine.INIT;
PurchaseLine."Document Type" := PurchaseHeader."Document Type"::Order;
PurchaseLine."Document No." := OrderNo;
PurchaseLine."Line No." := NextLineNo;
PurchaseLine.INSERT(TRUE);
PurchaseLine.VALIDATE(Type,PurchaseLine.Type::Item);
PurchaseLine.VALIDATE("No.", ItemNo);
PurchaseLine.VALIDATE(Quantity,Quantity);
PurchaseLine.MODIFY(TRUE);

Close the codeunit, click OK with the checked Compiled option.

Performance tip: to make the connector load data faster, set the Max page size parameter high enough to cover the size of the Transactions query. To do this, open the NAV Server Administration Tool, expand the tree in the left pane, select DynamicsNAV80 instance. Expand the OData Services tab, click the Edit button in the bottom, set the value in the Max page size field. For example, if the query returns over 1.3 million records, set it to 1,400,000. Click the Save button. Restart the NAV server.


Next: Dynamics GP

Download PDF

nav-connection-guide.txt · Last modified: 2018/11/02 16:34 (external edit)