Mar 22, 2015

Embedding EasyMorph projects into QlikView applications

We've added one more demo -- an example of QlikView Integration. It shows how data transformation logic can be moved from a QlikView loading script into an EasyMorph project, where it can be visually designed, modified and viewed. While it doesn't replace the loading script completely (yet) it demonstrates how core transformation logic can be made accessible for non-technical users, who can now explore and modify the logic in a visual way, without dealing with the script syntax.

The example is based on another EasyMorph demo -- Inc5000 with added export to QVD. Here is its transformation logic. Input and output transformations are marked on the screenshot below (click to zoom).

The EasyMorph project loads a text file (one file per state), maps state names from another file, does a few calculations and aggregations and exports the result into a QVD file. Here is the loading script with the project integrated (comments removed, download the example for the full version):

LOAD * Inline [
New York

LET pathEasyMorph = GetRegistryString('HKEY_CURRENT_USER\Software\EasyMorph', 'ApplicationPath');

let vCount = NoOfRows('States');

FOR I = 0 to vCount - 1

    LET State = Peek('State', I, 'States');
    //create input file for the EasyMorph project
    EXECUTE cmd /C copy /Y "Inc5000 $(State).csv" input.csv;
    EXECUTE $(pathEasyMorph) /c /run "Inc5000 for QlikView.morph";   

    //read the QVD generated by the EasyMorph project
        '$(State)' as State
    FROM output.qvd (qvd);


Since EasyMorph can't process a list of files yet (this feature will be added in future releases) a simple workaround is used -- a cycle, that iterates through a list of file names, and renaming.

For convenience the EasyMorph project can be opened right from desktop QlikView (there is a button for this in the example).

For server execution, you might need to specify the path to EasyMorph executable explicitly, since EasyMorph is usually installed under a user account and may not be available in the registry under QlikView Server's account.

While it's not shown in the example, you can also add a link to the HTML documentation automatically generated by EasyMorph when it runs a project with /doc parameter from command line (see help on this). In this case users will be able to see the documentation right in the web-browser, next to the application. Or, right in the application, using an extension for web page embedding.

Downloadable example of QlikView integration
EasyMorph Overview