Perfion Release2ERP for NAV 2009 allows you to import and persist information from Perfion to the NAV environment.

This document will describe the installation and configuration of Perfion Release2ERP for the typical NAV environment.

If you have special use cases or need custom setup tailored to your needs, please contact your Perfion partner for more information.

FAQ regarding installation of Perfion Release2ERP for NAV

Open

Introduction

Perfion Release2NAV allows you to import and persist information from Perfion to the NAV environment.

This document will describe the installation and configuration of Perfion Release2NAV for the typical NAV environment. If you have special use cases or need custom setup tailored to your needs, please contact your Perfion representative for more information.

General Considerations

A Word of Caution

Any changes made to you ERP system should be tested in a proper test environment before being deployed to the live ERP system. Please consult with your Microsoft Dynamics Partner about the changes required to implement this software, before continuing further.

Supported NAV Versions

The following versions of Microsoft Dynamics NAV is supported:

Microsoft Dynamics NAV 2009

Supported NAV Clients

The Classic and Role Tailored Client (Also known as the Windows client) are supported.

Prerequisites

The Service Layer server (if used) needs Microsoft .Net 4.5 installed.

Installation

Release2NAV is very simple to install. Just import the Fob file and handle any conflicts you might have.

Configuration

Release2NAV is a very versatile tool that can be configured to fit many different use cases. In this document, we will show simple examples that illustrate what is possible and discuss the options available.

Basic settings in Release2NAV

Run Form 81002 Perfion Setup.

You should see a form like this:

Open

For most, the default values will be perfectly fine.

Log: The log field is where you choose what type of events to log. The options are: Error, Success, All

Log Period: this field is where you set how far back in time the log entries will be kept. It is expressed as a date formula DateFormula Property - Dynamics NAV

Setting up a Perfion Connection for Release2NAV

Run Form 81003 Perfion Connections

You should see a form like this:

Fill in the fields to match your setup.

Code: This is the code for this connection.

Description: Enter a description of this connection.

Connection String: Enter the full URL of the API service. Example: http://url.com:8080/Perfion/GetData.asmx

Image Server: Enter the full URL of the API Image service. Example: http://url.com:8080/Perfion/Image.aspx

Setting up a Release2NAV Integration

Run Form 81007 Perfion Integration Card

You should see a form like this:

The General Section

This section contains the general setup elements for the integration.

Code: This is the code for this integration.

Connection Code: Here you select which connection the integration will use to import data.

Description: Enter a description of this integration.

Last Run Date: This field is not editable; it will automatically be updated whenever the integration is run successfully.

The Query Section

This section contains the settings that are related to the query of the API service.

For information about how to write a query, please see the Perfion API documentation.

In addition to that: Any instance of %LASTRUN% will be replaced by the Last Run Date value.

Here is an example query:

Here is an overview of the fields in the query section:

Query Type: This indicates the type of query storage used. Currently this is limited to File only.

Query File Name: This is the full path to the text file that contains the query that is sent to the API service.

Record Root Node: XPath that is used as root node in the result set of the query.

The Field Mapping Section

This is what we are here for: Mapping data fields from Perfion to data fields in NAV. It is simple, but there are a few things you have to keep in mind.

Each line represents one value mapped from Perfion to NAV.

To map anything in to a table in NAV, you have to map all primary key fields of the destination table as a minimum.

Here is an overview of the fields:

Table: This is the number of the table that the line is pointing to.

Table Caption: This is the caption of the table that the line is pointing to. When Table No. is changed this is automatically filled in.

Field No.: This is the number of the field that the line is pointing to.

Field Caption: This is the caption of the field that the line is pointing to. When Field No is changed this is automatically filled in.

XPath: This is the Xml XPath to the value that is being imported from Perfion. This is a relative path from the root node that was declared in the Record Root Node field, in the Query section.

Validate Data: This has 3 settings: Blank means no validation. When Different means that the data will be validated if the new value is different from the old value. Always means that the value will be validated every time the integration is run.

Accept Max. Length: When enabled, the value from Perfion will be truncated to the length of the destination field if necessary.

Default Value: This is a constant value that will be inserted in the destination field if no value is was found in the XPath of the data from the API service.

Conversion Code: If this is set to a valid Conversion Code, then the selected conversion will be applied to the value being imported.

Setting up a Release2NAV Conversion

Run Form 81004 Perfion Conversion Card

You should see a form like this:

The General Section

This section contains the general setup elements for the conversion.

Connection Code: This is the Connection Code for this conversion.

Code: This is the code for this conversion.

Description: Enter a description of this conversion.

The Values Section

Here you will find the Conversion Lines. Each line describes one value conversion.

The lines have two columns:

Perfion Value: This value is used to compare values from Perfion against. Values are case sensitive and only exact matches are considered.

Microsoft Dynamics NAV Value: If a match has been made then this value is used in NAV.