Perfion ERP Add-in for Dynamics 365, Finance and Operations allows you to quickly lookup related information in Perfion, from within the D365 FO environment.

This document describes the configuration of Perfion Add-in for the typical D365 FO 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 D365 FO versions

The following versions of Microsoft Dynamics D365 FO is supported:

• 7.0

• Release 1611

• July 2017 update

• 7.3

• 8.0

• 8.1

• 10.0

Prerequisites

Perfion Web Client needs to be installed and available to the client computers.

Installation of the Perfion Web Client is described in separate documentation.

Installation

Conventions

Here is a description of the conventions and assumptions used in this section.

• Location of .axmodel file

  • It is assumed that the .axmodel file is placed in C:\Temp\perfion

• Location of modelutil.exe

  • It is assumed that the modelutil.exe file is placed in K:\AosService\PackagesLocalDirectory\Bin

• Metadata Store Path

  • It is assumed that the metadata store path is this: K:\AosService\PackagesLocalDirectory

• System Rights

  • You will need RDP access to the D365 FO server with administrative rights. All commands should be executed in a Command Line Interface running with administrator rights.

Installing a .axmodel

Open a command prompt with administrator rights and change to the K: drive.

C:\windows\system32>k:

Go to the Bin folder of the metadatastore.

K:\>cd AosService\PackagesLocalDirectory\Bin

Run modelutil.exe with the following command:

K:\AosService\PackagesLocalDirectory\Bin>modelutil -import

-metadatastorepath="K:\AosService\PackagesLocalDirectory"

-file="C:\Temp\perfion\MyModel.axmodel"

If all goes well you should get this message:

Installation Finished Successfully

Upgrading a .axmodel

Open a command prompt with administrator rights and change to the K: drive.

C:\windows\system32>k:

Go to the Bin folder of the metadatastore.

K:\>cd AosService\PackagesLocalDirectory\Bin

Run modelutil.exe with the following command:

K:\AosService\PackagesLocalDirectory\Bin>modelutil -delete

-metadatastorepath="K:\AosService\PackagesLocalDirectory"

-modelname=MyModel

You will be prompted:

Are you sure you want to delete model PerfionRemotes? (Y/N)

Press y to continue.

Run modelutil.exe with the following command:

K:\AosService\PackagesLocalDirectory\Bin>modelutil -import

-metadatastorepath="K:\AosService\PackagesLocalDirectory"

-file="C:\Temp\perfion\MyModel.axmodel"

If all goes well you should get this message:

Installation Finished Successfully

It should all look something like this:

Configuration

Menu structure

Installing Perfion Add-in adds a new sub menu to System administration > Setup named Perfion. This new menu contains a menu item named Perfion Add-in configuration.

Configuring the module

Open the Perfion Add-in configuration menu item to create and maintain the Add-in configuration.

The configuration table consists of the following five fields:

• Table name: The D365 FO table on the ERP side of the mapping

• Field name: The D365 FO field name on the ERP side of the mapping holding the key value in the table chosen in Table name.

• Base URL: The base URL of the Perfion WebClient.

• From feature: The base feature on the Perfion side of the mapping holding items corresponding to the D365 FO table selected in Table name.

• Key feature: The configured feature on the Perfion side of the mapping holding the key value corresponding to the D365 FO field chosen in Field name.

• Related information pane width: Change the width of information pane to show more information horizontally width value is defined with “pixels” e.g., 400px.

• Custom height: Change the height of the Perfion Addin factbox to show more information vertically, height is defined in “pixels” e.g., 800px.

The example above shows a typical product-to-product configuration. It is possible to add more lines to the configuration if you want to link other D365 FO tables to corresponding structures in Perfion. An example of this could be if you have customer information both in D365 FO and in Perfion. You can then show Perfion customer information inside D365 FO by adding a new line to the configuration and integrate the Perfion add-in on a customer form in D365 FO (see next chapter).

Perfion Web Client 5.0+

With release of version 5.0 of the Perfion Web Client, there has been made some changes on how the Factbox works within Business Central.

When installing the Web Client using the installation wizard, a checkbox “Use Factbox” must be checked in order for the Addin to show factbox content in Business Central.

Use Factbox: Enable this if your use the factbox in Business Central

Integrating Perfion Add-in on a new form

The module comes with the add-in integrated to the products and released products list pages.

It has been placed in the right-hand part section of the form:

Adding the Add-in to an existing form

In the following section, we will add the Add-in part to an existing list page (EcoResProductListPage).

1. Open Visual Studio and find the form you want to customize. Create a new extension for the form.

2. Right click the Parts node of the form and select “New Form Part Reference”

3. Configure properties for the new reference in the property sheet and link it to the

PF_PerfionAddInControlPart menu item

4. Specify the data source you want to send to the form part. This is the table D365 will look for in the configuration setup in order to find the Perfion URL and feature setup.

Build the solution and open a new workspace to see that the Perfion form part has been added to the form. Remember to create a configuration record for the table specified for the form part reference. The Perfion form part will only load a URL if a configuration exists.