Export Tables To CSV Post Plugin

Download Zip: ExportTablesToCSVPostPlugin

Files included:

ectools.zip
ectools_sisense_ver<6.4.zip - (only for versions 6.4 and below)
python-2.7.11.amd64.msi
config_example.txt
EC_export.dll

This post explains how to install and configure the post plugin for exporting tables into CSVs . This plugin enables the user to define which tables will be exported into CSVs during the build finalization process. With this plugin you will be able to:

Reduce build time. For example, a user can store historical data in a CSV file and just union it with the new data on every new build (handy when pulling data from web services).
Define and maintain a unified repository cube. In cases when several cubes need to use the same data table, the user can define one cube which create the data table, all other cubes will use the CSV extracted from it.
Push the data into other reporting systems. Some customers also use the Elasticube manager as an ETL tool and transfer the data forward.

Important! The Build process will not end until the post plugin has finished. Exporting millions of rows to CSV files may take a considerable amount of time and thus will result with a longer ElastiCube build process.

Steps

Step 1: Download and install Python x64 on your machine.

Note! In order to run the plugin, an installation of Python x64 is required.

Install The attached Python version.
In the Windows Search Box, located next to the Start button, type in Edit the system environment variable and click on it.
Under Advanced, click on the Environment Variables button.
Under the System Variables pane, click on Path variable and then click Edit.
In the Edit environment variable window, click on New and add C:\Python27 at the bottom of the list.

Step 2: Install the Export to CSV Post plugin

Create a new directory in C:\Program Files\Sisense\Prism\Server and name it Plugins.
Download the EC_export_dll dll file and place it in C:\Program Files\Sisense\Prism\Server\Plugins
Right Click the DLL file, and choose Properties.
In the General pane, if a button with a Unblock caption exists, click on it (now Windows allows executing the DLL). See image below:
Extract the contents of the ectools.zip into C:\Program Files\Sisense\Prism
Open Services and restart the ElastiCubeService Service.

Step 3: Executing the plugin in the Elasticube Manager

Once in ElastiCube Manager, open ElastiCube ==> Pre & Post Execution Plugins.
Add to the post plugin section a new plugin called EC_export.
Click on Add to configure how the plugin should behave:

<Attributes path="c:\data" 
csv="true" 
tables="brand,categorypath"
pythonPath="C:\Python27\python.exe" 
timestamp="true">
</Attributes>

These are the attributes we can add:

path - the directory where the TDE/CSV files will be created at. (e.g - path="C:\TDE")
row_limit (optional) - limit the number of rows imported from each table in the Elasticube. (e.g - row_limit="1000" , only 1000 rows will be imported from each table).
csv (optional) - determines if TDE files will be created, or CSV files instead. TDE files are automatically created if this attribute is not found. (e.g - csv="true", CSV files will be created).
tables (optional) - determines which tables will be imported from the ElastiCube. Tables are separated by comma. If this attribute isn't found, all the tables will be imported. (e.g - tables="brand,categorypath" , "brand" and "categorypath" tables will be the only ones imported.)
pythonPath (optional) - direct path to Python.exe (if PATH variable is not working on your environment)
timestamp (optional) - adds timestamp to CSV filename

Step 4: Run Build.

In the build's finalizing step the plugin execution will appear in the ElastiCube manager log window. In the ElastiCube Manager console:

Andrew Block December 12, 2017 15:35

I show both a ectools zip and an ectools_sisense_ver6.4 zip, I am assuming if we are on 6.4 or higher we would extract the 6.4 zip into C:\Program Files\Sisense\Prism?

Yoni Lerner December 14, 2017 14:19

For higher than 6.4 use ectools.zip

Oxana Noa Umansky December 14, 2017 14:28

Hi Andrew,

Thanks for your comment. To add to Yoni's reply and clear any confusion I've also updated the post (see at the beginning) with the following:

Sonal Bansal March 15, 2018 05:13

We configured the above plug in and while executing the build , we are getting below error:

Can you help me resolve this error?

Regards,

Sonal

Oxana Noa Umansky March 15, 2018 13:02

Hi Sonal,

I'll create a support ticket for you, so that our team can investigate this issue.

You'll get a confirmation email with all the relevant information. You can also track any correspondence on this ticket via "My Activities".

Thanks,

Oxana

Maxim Havva April 04, 2018 22:03

Hi Oxana,

Can you confirm if the plugin is working with the 7-th version of Sisense?

I was using it successfully with older versions, but now on 7-th it says "failed to find the plugin"

Have any dependencies changed?

Just to clarify: all the contents of the ectools.zip is wrapped into "ectools" folder. I placed it into C:\Program Files\Sisense\Prism so the path looks like:

C:\Program Files\Sisense\Prism\ectools\BuildTester\ ..

Maxim Havva April 04, 2018 22:19

Nevermind, I figured this out,

best regards

Javier Irazazabal June 22, 2018 12:03

Hi all,

Running the plugin, I'm getting an error: "Directory name not valid"

I've tryed with several CSV's data target, but getting the same error.

Do you have an idea about this issue cause?

Thanks in advance!

Colton Porter August 14, 2018 20:56

I am getting the same issue. Can anyone help?

Javier Irazazabal August 15, 2018 09:20

Colton Porter I have just solved it reviewing the installation files, to be sure that every file and folder should be located in the right place. Doing this, I put the plugin to work. Hope it helps

GEHC Large Dev September 27, 2018 16:40

Just to summarize the solution to the error "Directory name not valid" like it appears on the screenshots above. This error happens when the ectools folder is inside another ectools folder due to the unzip.

To work the path should be C:\Program Files\Sisense\Prism\ectools\BuildTester\