DO UMENTATION N DS QLIKVIEW ONNETOR 1.6 · Architecture ... 1.1 Overview The NC BDS QlikView...

DOCUMENTATION NC BDS QLIKVIEW CONNECTOR 1.6.0

COPYRIGHT © NAVAX CONSULTING GMBH MARCUS JOCHER | HARALD MAYR | BERNHARD LEITNER

EURO PLAZA | TECHNOLOGIESTRASSE 8 | 1120 WIEN TEL.: +43 50 8383-0 | FAX: +43 50 8383-199

E-MAIL: [email protected]

mailto:[email protected]

DOCUMENTATION

NC BDS QLIKVIEW CONNECTOR 1.6.0

4relation | Deutschland | Österreich | Schweiz | Polen Seite 2 von 29

DISCLAIMER

This handbook serves for information purposes only. In case of using the manual for other purposes 4relation Consulting GmbH rejects each guarantee because of special and defective titles.

4relation Consulting GmbH rejects each adhesion for direct and indirect damage – no matter if it is from contract or from law -, which can develop in connection with application and other use of the Handbook, and any errors and omissions in this publication. This Handbook can be changed at any time if necessary without previous announcements by 4relation Consulting GmbH.

The content of this Handbook is protected by copyright. Without written permission of 4relation Consulting GmbH no part of this documentation may be multiplied or transferred for any purposes no matter which way, electronically or mechanically, it happens.

Microsoft Dynamics NAV, Microsoft Dynamics AX, Microsoft Dynamics CRM, Microsoft SharePoint, QlikView and Corporate Planner are registered trademarks. Further mentioned product and company names may be protected by copyright terms of their legal owners.

In this handbook is a version whose contents may change yet. These changes occur without prior notice. This handbook may be used only for internal purposes. Disclosure to third parties.

DOCUMENTATION



Content

1. Introduction ........................................................................................................................... 5

1.1 Overview .................................................................................................................................................. 5

1.2 Target audience ....................................................................................................................................... 5

1.3 Structure .................................................................................................................................................. 5

1.4 Versions ................................................................................................................................................... 5

2. Features ................................................................................................................................. 6

2.1 Backend independent Features ............................................................................................................... 6

2.1.1 Standard Edition ................................................................................................................................................ 6

2.1.2 Enterprise Edition.............................................................................................................................................. 6

2.2 Features specific for backend system Microsoft Dynamics NAV ............................................................ 6

2.2.1 Standard Edition ................................................................................................................................................ 6

2.2.2 Enterprise Edition.............................................................................................................................................. 6

3. Architecture ........................................................................................................................... 7

4. Supported platforms & software/hardware requirements ...................................................... 8

4.1 Specific for Dynamics NAV ....................................................................................................................... 8

5. Licensing & Versions ............................................................................................................... 8

6. Installation & Configuration .................................................................................................... 8

7. Uninstallation ......................................................................................................................... 9

8. Upgrades ................................................................................................................................ 9

8.1 Upgrade from demo to Standard/Enterprise Editions ............................................................................ 9

8.2 Add backend logic functionality to existing system ................................................................................ 9

8.3 Upgrade from Standard to Enterprise Edition ......................................................................................... 9

9. Operation & Maintenance ...................................................................................................... 9

10. Usage ................................................................................................................................. 10

10.1 Standard Edition .................................................................................................................................. 10

10.1.1 Starting the wizard ........................................................................................................................................ 10

10.1.2 Manage solution ........................................................................................................................................... 10

10.1.3 Navigation between wizard steps ................................................................................................................. 10

10.1.4 Connect & Login ............................................................................................................................................ 11

10.1.5 Global Settings .............................................................................................................................................. 12

10.1.6 Statement Management ............................................................................................................................... 13

10.1.7 Table Selection .............................................................................................................................................. 14

10.1.8 Related Tables ............................................................................................................................................... 15

DOCUMENTATION



10.1.9 Field Selection ............................................................................................................................................... 16

10.1.10 Filters .......................................................................................................................................................... 17

10.1.11 Sorting ......................................................................................................................................................... 18

10.1.12 Statement Preview ...................................................................................................................................... 18

10.1.13 QlikView script ............................................................................................................................................ 19

10.1.14 Final result in QlikView................................................................................................................................ 20

10.2 Enterprise Edition – Delta Load/Multisystem Load ............................................................................. 21

10.2.1 Global Settings .............................................................................................................................................. 21

10.2.2 Statement Management ............................................................................................................................... 22

10.2.3 Table Selection .............................................................................................................................................. 23

10.2.4 Field Selection ............................................................................................................................................... 24

10.2.5 QlikView script .............................................................................................................................................. 24

10.2.6 Final result in QlikView .................................................................................................................................. 25

10.3 Enterprise Edition – Calculated Tables ................................................................................................ 25

10.3.1 Table Selection .............................................................................................................................................. 26

10.3.2 Field Selection ............................................................................................................................................... 26

10.3.3 Filters............................................................................................................................................................. 27

10.3.4 Final result in QlikView .................................................................................................................................. 28

10.4 Standalone application ........................................................................................................................ 28

10.5 Messages ............................................................................................................................................. 29

10.5.1 Resolve all/Resolve Line ................................................................................................................................ 29

11. Backup & Restore solutions/projects and scripts ................................................................. 29

DOCUMENTATION



1. Introduction

1.1 Overview

The NC BDS QlikView Connector is used to establish the connection to the desired Microsoft Dynamics NAV System via NC Business Data Service by unique System ID and to generate QlikView load scripts for importing table data using NC Business Data Service.

The purpose of this document is to give an overview of features, architecture, supported platforms, requirements, licencing & options, installation & configuration, uninstallation and operation & maintenance for the NC BDS QlikView Connector.

1.2 Target audience

This document is intended for end users and consultants which install and use NC BDS QlikView Connector.

1.3 Structure

This document contains description for Standard and Enterprise Editions. Enterprise only features are mentioned in the headline or in the first sentence in the text.

1.4 Versions

The placeholders “<sprint-year>” and “<sprint-number>” are used allover this document in version numbers for setup packages names and installed product descriptions. For example “… <sprint-year>.<sprint-number>.0” could be “… 15.22.0” for year 2015 and sprint number 22 in this year.

DOCUMENTATION



2. Features

2.1 Backend independent Features

2.1.1 Standard Edition

one unique connector wizard for various backend systems (e.g. Microsoft Dynamics NAV) management of multiple statements/scripts including import/export solution files to store all global settings and all statements selection of all available tables incl. translated table names easy usage of related master data records through table relations field selection with all fields of main and related records incl. field name translations custom filtering custom sorting statement/script preview starting from step table selection

multi-language wizard user interface currently translated for English and German

multi-language metadata provides all available translations for table names, field names, …

security system usage of global filters to define user specific security

generation of QlikView script converts loaded data automatically to QlikView specific data types many customization possibilities using settings

2.1.2 Enterprise Edition

Multisystem Load (data is loaded from multiple backend systems into one output table) Delta Load (only records which have been modified since last load are added or updated) Comfort selection for subsidiary tables

2.2 Features specific for backend system Microsoft Dynamics NAV

2.2.1 Standard Edition

security system (reuse of standard NAV user role permissions for table access) access to multiple databases /companies through a single “Business Data Service” instance direct read access from Microsoft SQL database (including Flow Fields and even filters on them)

without NAS/WS communication overhead streamed communication for data load scenarios for low memory and CPU usage load balancing between any number of NAS (not required for NAV2013 and later) NC BDS Metadata system provides full information of Microsoft Dynamics NAV table/field

structures incl. translations (so called captions), datatypes, field constraints, flowfield definitions, table relations, …

supports usage of calculated flowfields provides option string translations for fields with data type option navigate through table relations to related records in arbitrary depth

(e.g. include sales header fields in a sales line statement)

2.2.2 Enterprise Edition

use of so called calculated tables

DOCUMENTATION



3. Architecture

The following picture gives an overview over a possible scenario.

For further information on [NAVAX Business Data Service] see Business Data Service documentation (3. Architecture).

In this scenario read access on data from all configured Microsoft Dynamics NAV systems is accessible in QlikView through NC Business Data Service using NC BDS QlikView Connector.

The connection is configured using NC BDS Connector Wizard utilizing the metadata presented by NC Business Data Service.

SUPPORTED CLIENT TYPES

DOCUMENTATION



4. Supported platforms & software/hardware requirements

supported operating systems: ▫ Microsoft Windows 7 (x86/x64) ▫ Microsoft Windows 8 (x86/x64) ▫ Microsoft Windows Server 2003 R2 (x/86/x64) ▫ Microsoft Windows Server 2008 R2 (x64) ▫ Microsoft Windows Server 2012 (x64)

required software/licences: ▫ QlikView, version 10 or higher ▫ Microsoft .NET Framework 4 ▫ NC Business Data Service <sprint-year>.<sprint-number>.0 & licence (see NC Business Data

Service documentation) required hardware depends on the following factors:

▫ required memory depends on count of used backend systems ▫ see QlikView documentation for detailed information

4.1 Specific for Dynamics NAV

supported Dynamics NAV versions & required software/licences (see NC Business Data Service documentation 4.1 specific for Dynamics NAV)

5. Licensing & Versions

The NC BDS QlikView Connector has 3 different licensing options

DemoQV (for Test/Demonstration purpose only) similar to StandardQV except username and password are always “demo”

StandardQV (see chapter 2 Features for detailed overview) EnterpriseQV (see chapter 2 Features for detailed overview)

For detailed information on licensing options see NC Business Data Service documentation (.1 Licencing, ClientAppQVConnector).

6. Installation & Configuration

for 32 bit Windows Systems create “C:\Program Files (x86)\Common Files \QlikTech\Custom Data” copy the install directory “BDS_QV_Connector_x86_V_<sprint-year>_<sprint-number>_0”

(the whole directory, not only the content) to the newly created folder for 64 bit Windows Systems

create “C:\Program Files\Common Files\QlikTech\Custom Data” copy the install directory “BDS_QV_Connector_x64_V_<sprint-year>_<sprint-number>_0”

(the whole directory, not only the content) to the newly created folder

DOCUMENTATION



7. Uninstallation

for 32 bit Windows Systems delete the directory “BDS_QV_Connector_x86_V_<sprint-year>_<sprint-number>_0” from

“C:\Program Files (x86)\Common Files \QlikTech\Custom Data”

for 64 bit Windows Systems delete the directory “BDS_QV_Connector_x64_V_<sprint-year>_<sprint-number>_0” from

“C:\Program Files\Common Files\QlikTech\Custom Data”

8. Upgrades

8.1 Upgrade from demo to Standard/Enterprise Editions

See NC Business Data Service documentation (8.1. Upgrade from demo version to full version) for detailed information.

8.2 Add backend logic functionality to existing system

See NC Business Data Service documentation (8.2. Add backend logic functionality to existing system) for detailed information.

8.3 Upgrade from Standard to Enterprise Edition

To upgrade from Standard to Enterprise Edition import your Enterprise Edition enabled license file to BDS configuration file and restart NC Business Data Service.

See Business Data Service documentation (6.3.3.3 License) for detailed information how to import licenses.

9. Operation & Maintenance

For operation of the NC BDS QlikView Connector the following points must be ensured:

NC Business Data Service must be running and appropriate configured NC Business Data Service (IP-Adress/Port) must be reachable from client

For an overview on NC Business Data Service configuration also watch the following video tutorials:

BDS_Video_MetaData_add_new_NAV_Company_to_BDS_V_1_2_0_EN.wmv

BDS_Video_MetaData_update_existing_NAV_Company_at_BDS_V_1_2_0_EN.wmv

DOCUMENTATION



10. Usage

This chapter describes the usage of NC BDS QlikView Connector with one example for Standard Edition and two examples for Enterprise Edition.

These examples are executed in the “Edit Script” window of QlikView.

10.1 Standard Edition

The example in this section demonstrates the usage of NC Business Data QlikView Connector utilizing Standard Edition features.

10.1.1 Starting the wizard

The following dialog is used for creating a connection to a custom connector (e.g. NC BDS QV Connector):

select “Navax.BusinessDataService.Client.Application.Common.BDSQVConnector.exe” start the wizard by clicking the “Connect…” button startup of the wizard can take a view seconds

Note: If you cancel the execution or it is canceled because an error occurred – wait a few seconds to get the correct error message! To restart the NC BDS QlikView Connector after an error occurred the button “Connect…” may has to be clicked twice.

10.1.2 Manage solution

The currently used solution can be saved at any time by using the buttons “Save“ or “Save as…” in the lower left corner. Previously stored solutions can be opened by using the “Open” button in the lower left corner. Please see information in section 9.5 Messages to handle import warnings and errors.

The file extension for NC Business Data Serive QlikView Connector solution files is “.bdssbs”.

10.1.3 Navigation between wizard steps

There are two ways to navigate between different wizard steps:

click on next/previous buttons in the upper right and left corners directly select any valid step using the selction box in the top center

DOCUMENTATION



10.1.4 Connect & Login

In this step details for the connection and credentials for the login are configured.

Name Description

Application Language

Language used for UI and comments in generated scripts (Currently available languages are en-US and de-AT)

Host IP-adress or hostname of NC Business Data Service instance

Port Portnumber on which the selected NC Business Data Service instance listens

Codepage

System ID List of configured systems available on the connected NC Business Data Service instance

Domainname

Username

Password

as defined in NC Business Data Service User table (for non-demo systems)

DOCUMENTATION



10.1.5 Global Settings

In this step general settings are configured.

Name Description

Data Language

Shows all available languages, which are available in the connected backend systems metadata. Data Language is initialized automatically based on the users session language or if unavailable based on the selected Application Language. Table and field names are translated to the selected language if available. Note: Only table/field names are translated. Data values are not translated!

Related Systems not allowed for Standard Edition, see 9.2.1 Global Settings

Use Translations if activated, table/field names are translated, otherwise technical names are used

Replace special charaters replaces or removes all special characters in table and field names

Table name as, Table field name seperator

configures how field names are qualified with table names

“Prefix” (e.g. “Customer_Name”) “Postfix” (e.g. “Name_Customer”)

Option Field Value

(Note: option field values are stored as integer values in the SQL database)

Translation: option field content is transferred as translated value Number: option field content is transferred as number Both: option field content is transferred as translated value and

number an additional field with postfix “_Internal” is created in the generated script which contains the number value

Keep Option Translation A mapping table is needed in the statement to map the option fields. This table does not remain in the data model. If this box is checked, an additional persistant table is created.

Default Option Field Value If the translation fails, a default value can be used instead. if not selected, the original value remains.

DOCUMENTATION



10.1.6 Statement Management

Statements in the current opened solution are managed here.

Changing current selected statement can be done either by selecting directly in the selction box above the statement list or by selecting the associated line.

Name and Description for the statement can be edited in the associated columns. Statements can be exported to a file and imported from a file individually (standard file extension

“.bdssbp” -. “NC Business Data Service Statement Builder Project”). Please see information in section 9.5 Messages to handle import warnings and errors.

Starting from this step a preview of the statement is displayed at the bottom, the statement can be copied to clipboard or exported as a text file and the statement can be executed for test purposes using the “Execute” button.

Store to QVD/Delta Load these options are only available in Enterprise Edition and are described in section 9.2 Enterprise Edition – Delta Load/Multisystem Load

DOCUMENTATION



10.1.7 Table Selection

The main table where data is fetched from is selected here (e.g. “Detailed Cust. Ledg. Entry”).

A Filter can be applied, to find tables. (e.g. all tables with “cust” as part of their name) Filtered columns include

Number Name Translation QV Name

Displayed tables can be reduced to only show tables with a message attached (for description of messages see section 9.5 Messages)

Data per DB indicates that this table does not contain data per NAV company Filter (Main Table) & ”Use selected as Main Table” button

this feature is only available in Enterprise Edition (see 9.2.3 Table Selection for further information) Resolve all Lines / Resolve Line (for a description on resolving Messages see section 9.5)

DOCUMENTATION



10.1.8 Related Tables

Related tables are selected here (e.g. “Customer” via “CustomerNo” from “Detailed Cust. Ledg. Entry”).

Note: Related tables is about selecting whole records – which are connected to the main table via table relations – not about selecting fields. It’s not possible to use related tables to navigate from “Customer” to “Detailed Cust. Ledg. Entry”.

This section is only visible if tables are related to the selected main table from the previous step. Multiple related tables can be selected in an arbitrary depth.

checking the “+/-” field shows related tables in reference to current line (expands to the next level) selecting an expanded related record will also select all related records from higher levels the alias of the table can be renamed (e.g. “CountryRegion_via_CountryRegionCode” to “Country”) a filter can be applied to find specific tables (e.g. all tables with “country” as part of their name)

filtered columns include: Alias Table Name Table Number Table Translation Related Table Name Related Table Number Field Name Field Number Field Translation

Resolve all Lines / Resolve Line (for a description on resolving Messages see section 9.5 Messages)

DOCUMENTATION



10.1.9 Field Selection

The fields where data is fetched from are selected here. Multiple fields of main record and all selected related records can be selected.

mandatory fields are selected automatically (System ID and all primary key fields) additional fields can be selected from the main record and all related records displayed fields can be reduced to show only selected displayed fields can be reduced to show only fields with messages attached to them (see 9.5

Messages for more information about messages) a filter can be applied to find specific fields (e.g. all fields with “country” as part of their name)

Filtered columns include: Record Name Table Number Table Name Table Translation Field Number Field Name Field Translation Target Field Name

Resolve visible Lines / Resolve Line (for a description on resolving Messages see section 9.5 Messages)

DOCUMENTATION



10.1.10 Filters

Filters applied to the fetched data are configured in this step. Filters are divided in filter groups and filter lines. A filter group can have multiple filter lines. The filter group represents the logical operator (And/Or) that connects the conditions represented by the different filter lines.

Note: It is impossible to use a filter line without at least one filter group.

Operator the logical operator for a group of conditions (filter lines in a filter group)

filter groups are added using the “Add Group” button Field

selection of a field on which to apply a condition Value

the value to compare against a Field for a condition filter lines are added using the “Add Line” button (only possible when a group or line is selected) filters groups or lines can be removed from the list with the button “Delete Group/Line” Resolve all Lines / Resolve Line (for a description on resolving Messages see section 9.5 Messages)

DOCUMENTATION



10.1.11 Sorting

In this step the sort order for the fetched data is configured.

Field data will be sorted based on the data in this field

Order Type direction in which data will be sorted (Ascending/Descending)

lines are added using the “Add Line” button order sequence in the list is altered with the buttons “Move up” and “Move down”

the order sequence in the list represents the sequence in which the order conditions are applied lines are removed from the sequence via the “Delete Line” button. Resolve all Lines / Resolve Line (for a description on resolving Messages see section 9.5 Messages)

10.1.12 Statement Preview

This step shows a final preview of the generated QlikView script including NC BDS statement.

DOCUMENTATION



10.1.13 QlikView script

When closing the wizard application by clicking the “OK” button the script is not stored, only the connection string to customer connector is inserted to the QlikView Script. Possible options to use the script of the current selected statement include:

copy to clipboard with the button “-> Clipboard” and paste it to the QlikView script save the generated statement to a text file using the button “-> Text File” and use it at a later time

When following the previous sections the script generated should look similar to the script below:

CUSTOM CONNECT TO

"Provider=Navax.BusinessDataService.Client.Application.Common.BDSQVConnector.exe;SystemID

=NAVDACH-602-1-NAS-

TEST;Username=demo;PageSize=50000;Host=srvapp_test;Port=8733;XUserId=cPJNSDD;XPassword=aS

fOJSVMNbbIB;";

DetailedCustLedgEntry_EntryType:

Mapping LOAD * INLINE [

DetailedCustLedgEntry_EntryType_Value, DetailedCustLedgEntry_EntryType_Name

0,

1, Initial Entry

2, Application

3, Unrealized Loss

4, Unrealized Gain

5, Realized Loss

6, Realized Gain

7, Payment Discount

8, Payment Discount (VAT Excl.)

9, Payment Discount (VAT Adjustment)

10, Appln. Rounding

11, Correction of Remaining Amount

12, Payment Tolerance

13, Payment Discount Tolerance

14, Payment Tolerance (VAT Excl.)

15, Payment Tolerance (VAT Adjustment)

16, Payment Discount Tolerance (VAT Excl.)

17, Payment Discount Tolerance (VAT Adjustment)

];

DetailedCustLedgEntry_DocumentType:

Mapping LOAD * INLINE [

DetailedCustLedgEntry_DocumentType_Value, DetailedCustLedgEntry_DocumentType_Name

0,

1, Payment

2, Invoice

3, Credit Memo

4, Finance Charge Memo

5, Reminder

6, Refund

];

DOCUMENTATION



// + generated - load script (DetailedCustLedgEntry)

DetailedCustLedgEntry:

LOAD

"System ID" & '_' & "Entry No." as _DetailedCustLedgEntry_PrimaryKey,

"System ID" as DetailedCustLedgEntry_SystemID,

"Timestamp" as DetailedCustLedgEntry_Timestamp,

"Entry No." as _DetailedCustLedgEntry_EntryNo,

APPLYMAP('DetailedCustLedgEntry_EntryType', "Entry Type", '<na>') as

DetailedCustLedgEntry_EntryType,

date("Posting Date") as DetailedCustLedgEntry_PostingDate,

APPLYMAP('DetailedCustLedgEntry_DocumentType', "Document Type", '<na>') as

DetailedCustLedgEntry_DocumentType,

"Document No." as DetailedCustLedgEntry_DocumentNo,

replace("Amount (LCY)", '.', '$(DecimalSep)') as DetailedCustLedgEntry_AmountLCY,

"Customer_via_CustomerNo.Timestamp" as Customer_via_CustomerNo_Timestamp,

"Customer_via_CustomerNo.No." as Customer_via_CustomerNo_No,

"Customer_via_CustomerNo.Name" as Customer_via_CustomerNo_Name,

"Customer_via_CustomerNo.City" as Customer_via_CustomerNo_City,

replace("Customer_via_CustomerNo.Balance (LCY)", '.', '$(DecimalSep)') as

Customer_via_CustomerNo_BalanceLCY,

"Country.Timestamp" as Country_Timestamp,

"Country.Code" as Country_Code

// manual fields - start

// manual fields - end

;

SQL

SELECT "System ID", "Timestamp", "Entry No.", "Entry Type", "Posting Date", "Document

Type", "Document No.", "Amount (LCY)",

Customer_via_CustomerNo."Timestamp", Customer_via_CustomerNo."No.",

Customer_via_CustomerNo."Name", Customer_via_CustomerNo."City",

Customer_via_CustomerNo."Balance (LCY)",

Country."Timestamp", Country."Code"

FROM "Detailed Cust. Ledg. Entry",

"Customer" FN "Customer No." AS Customer_via_CustomerNo,

"Country/Region" FN Customer_via_CustomerNo."Country/Region Code" AS Country

WHERE (("Document Type" = '"Invoice"') OR ("Document Type" = '"Credit Memo"'))

ORDER BY "Posting Date"

;

// - generated - load script (DetailedCustLedgEntry)

10.1.14 Final result in QlikView

After executing the script the final result can be viewed and used.

DOCUMENTATION



10.2 Enterprise Edition – Delta Load/Multisystem Load

The example in this section demonstrates the usage of NC Business Data QlikView Connector utilizing Enterprise Edition features except “Calculated Tables”. For an example and description on calculated tables see section 9.3 Enterprise Edition – Calculated Tables.

Steps not mentioned in this chapter were already treated in section 9.1 Standard Edition.

Features shown in this example include:

Multisystem Load: Data is loaded from multiple backend systems and merged into one output table.

Delta Load: Only records which have been modified since last load are added or updated. Whether a record is modified or not depends on the SQL timestamp.

Comfort selection for subsidiary tables

10.2.1 Global Settings

Multiple related backend systems can be selected. A related backend system is a system with equal metadata configured in NC Business Data Service.

DOCUMENTATION



10.2.2 Statement Management

Enterprise Feature Delta Load enabled for the selected statement.

Store to QVD data is stored to a seperate .qvd

Delta Load only modified records will be fetched Note: needs Store to QVD a file DeltaLoad.qvd which contains the last timestamp for all loads will be generated

DOCUMENTATION




In this section the Enterprise Edition feature “Comfort selection for subsidiary tables” is described. This is a feature to help find e.g. transaction data tables using the corresponding master data table.

Note: This is step differs from the rest of this Enterprise Edition example because “Detailed Cust. Ledg. Entry” is not a master data table therefore it would not show corresponding transaction data tables.

Instructions for searching a transaction data table starting from master data table “Job”:

search the table using filter “job” to find table 167 mark the table “Job” (blue background) click the “Use selected as Main Table” button the text “Job (167)” is used as “Filter (Main Table)” and the value in the field “Filter” is removed “Filter (Main Table)” is read only, the content can be removed using the “Reset” button transaction data tables for the table “Job” are displayed search for tables using “entry” as Filter and select table “Job Ledger Entry” to continue

DOCUMENTATION




The selection of calculated fields is disabled for Enterprise feature Delta Load because the content on which the calculated fields value is based is stored in different tables. Changing one or many of these records does not affect the timestamp of the calculated field.

In this example the field “Balance (LCY)” can not be selected because it is a calculated field.

Note: Calculated field contents should only be used for static reports (e.g. for presentations) but not for data mining.

10.2.5 QlikView script

The QlikView script is generated similar to the Standard Edtion example (see section 9.1.13). Differences include:

generated code to store to QVD generated code for Delta Load generated code for Multisystem Load

DOCUMENTATION




The first screenshot shows the progress of a full load of the example script in QlikView. The second screenshot shows the progress of the Delta Load of the example script in QlikView.

10.3 Enterprise Edition – Calculated Tables

The example in this section demonstrates the usage of NC Business Data QlikView Connector utilizing Enterprise Edition features.

Steps not mentioned in this chapter are described under 9.1 Standard Edition.

Calculated tables are developed in Microsoft Dynamics NAV and the metadata has to be configured using NC BDS Metadata Function Definition Editor. Calculated Tables do not exist in the SQL database but can be querried similar to a normal table. Data is calculated direct in Microsoft Dynamics NAV in a defined function.

For different types of functions and how to utilize and configure them see NC BDS Metadata Function Definition Editor documentation.

DOCUMENTATION




Calculated Tables have negative table numbers (e.g. -2 for “DemoCalcItemAvailabiltyLocation”) In the table list Calculated Tables are marked with the column “Calculated” checked.


Field Selection equals standard Field Selection (see section 9.1.9 Field Selection) except that fields configured as “Output” of the calculated table are preselected automatically.

DOCUMENTATION



10.3.3 Filters

Configuration of Filters equals standard Filter configuration (see section 9.1.10 Filters) except that a Dummy Filter Line is preconfigured for each fields configured as “Input” of the calculated table.

The preconfigured Line has to be removed manually. Each field configured as “Input” of the calculated table must be set as a Filter Line in the

preconfigured Filter Group.

DOCUMENTATION




After executing the script the final result can be viewed or used.

10.4 Standalone application

The NC BDS QlikView Connector can run as a standalone application (e.g. for generation of statements/solutions when QlikView is not needed/present).

To run the NC BDS QlikView Connector as a standalone application the following steps have to be executed:

locate “Navax.BusinessDataService.Client.Application.Common.BDSQVConnector.exe” in the folder where NC BDS QlikView Connector is installed (e.g. “C:\Program Files\Common Files\QlikTech\Custom Data\BDS_QV_Connector_x64_V_<sprint-year>_<sprint-number>_0” for a 64 bit version)

start “Navax.BusinessDataService.Client.Application.Common.BDSQVConnector.exe” proceed as described under 9.1 Standard Edition on the step Global Settings choose “QlikView” as target system

DOCUMENTATION



10.5 Messages

When opening a solution or project file messages can be shown on the corresponfing lines on different steps if metadata has changed (e.g. choosing a different system with different metadata while keeping a statement). These Messages indicate incompatibility between the statement and the selected systems metadata.

Messages are classified as warnings or errors.

10.5.1 Resolve all/Resolve Line

On steps where messages can appear, two buttons are placed below the respective list:

Resolve all resolves all messages in the active step

Resolve Line resolves messages for the current selected line

When resolving messages either corresponding contents are reset to the original metadata or lines are deleted if not longer existent in the metadata.

11. Backup & Restore solutions/projects and scripts

It is strongly recommended to create backups of solutions and/or projects:

solution backup -> see 10.1.2 Manage Solution

project backup -> see 10.1.6 Statement Management

Note: It is not adviced to create only backups of generated QlikView scripts – always save the solution or project using NC BDS QlikView Connector.

To restore QlikView scripts after reinstall the old scripts can be reused. For restore after product upgrade all generated script parts in QlikView scripts must be recreated using the backed up solution/project files. While opening these files in the Wizard the internal structure is updated to match new versions needs.

Date post:	27-Jul-2018
Category:	Documents
Upload:	buihanh
View:	218 times
Download:	0 times

DO UMENTATION N DS QLIKVIEW ONNETOR 1.6 · Architecture ... 1.1 Overview The NC BDS QlikView...

Documents