Using Script to output a txt, csv, xml, or xlsx file

Hello Anthony,

thanks for the new interesting topic in this forum. First of all I have to note that the mentioned limitation (access to local files) is rather a limitation of a Webbrowser sandbox, not the JavaScript language itself. And since we are running our own JavaScript engine in our environment, we are not affected by such a limitation. So in principle you are free to write to local files.

However, JavaScript has no API to handle files - but Java has so you have to script against the Java IO API. Before you do that, maybe the Clipboard is an option to exchange data. Please find attached a sample script I wrote a while ago that as an example extracts some data from system models and put them as CSV to the clipboard.

Happy Scripting

Jan

All comments

Hello Anthony,

Happy Scripting

Jan

Hi all,

is there a script/command equivalent to "Generate table report" in the Medini list editor to generate an excel table out of a selected list?

Thank you!

Daniel

Hi Daniel,

so you are looking for something that doe snot produce CSV but Excel instead? Is that the right understanding? I foudn this example here which combines the excel.js way of using a callback object and some iteration. The other sample directly writes the Excel file, you may combine both if you want.

Happy Scripting

Jan

Hi Jan,

many thanks for the scripts. I could solve my task with it.

Actually I wanted to know if there are short commands which replace the whole file generation (format independent) equivalent to the buttons "Generate table report" or "Auto-Generate M2Doc Report".

Thank you!

Daniel

Hi Daniel, they are not, I'm afraid.

However, maybe there are some low hanging fruits here. Any sggestion what would make sense to you?

Really a CSV export in the tables for example, to the clipboard?

Jan

Hi Jan,

thanks for your answer and supply.

For example we have in our Medini model different reports to create. It would be great if they could be started in a row by a script. Or to integrate the report generation or excel/csv file generation in our script based process steps. All that with the final objective that the files are generated and stored in a specific folder.

Thank you,

Daniel

Hi Daniel,

so it is more about automation of reports, right? Are your reports all BIRT based at the moment? I mean, you use table reports (which are internally BIRT based) and also custom reports I assume based on BIRT, is that correct?

Jan

Hi Daniel,

if your reports are m2doc based, there is an action in the "Report" menu at project root node named "Auto-Generate All M2Doc Reports", maybe that is exactly what you are looking for.

Happy Reporting

Jan

Hi Daniel,

we were working on a small m2doc.js project, and were able to achieve a first milestone.

Find with this post the m2doc.js library and a small test sample. The library

Is meant to automated m2doc based reporting
Does NOT support yet an easy creation of a new m2doc configuration
Can run an m2doc based report from a script for a fully configured configuration, in that case the report output goes to the file specified in the config
Can run an m2doc based report from a script for a configured configuration + an optional output file, in that case the report output goes to specified file ignoring whats configured in the config

Please give it a try and report any problems here to extend and improve the library.

Happy Reporting

Jan

Hi Jan,

I tested your script. The result is exactly what we were looking for :-)

Many thanks for your support!

Daniel

Glad it works!

Jan

medini_1075354657

Hello Jan,

The script m2doc.js you shared cannot be open. It gives me a message that I do not have permission to open the file. Is it intentional, or you think there is a problem on my side?

Milorad

Milorad, I am pretty sure it is on your side, many Computers dont like downloaded JavaScript files these days.

Try to rename it maybe.

Jan

medini_1075354657

Renaming the script worked. Thanks, Jan

Hello,
I am using 2025 R1.
When I run the script within medini for generating the m2doc, it works. But when I run it via command line, the docx is not generated and there is no log on the command window.

A disclaimer is thrown every time I run the batch script, but files are not generated.

Am I missing something?

mediniAnalyze.exe" script -s TestM2DocReports.js -f file.mprx -useDefaultWorkspace -nosplash

Hi Varma,

the disclaimer is coming because the script uses some internal APi which was disclosed to get the m2doc reporting done. Thre are some ways to avoid that dialog. It depends a bit on the way you deploy the script. Have you added th script to the MPRX? So its basically part of the MPRX or is the script "living" outside. Both ways are possible.

About the point that the report is not generated... is it possible to post he script here? I mean, is there anything special about it?

You may check the error log of the eclipse workspace, maybe some error is logged there. Either omit the -useDefaultWorkspace and chose a workspace of your choice to have the error logged there or navigate to the default workspace. Thats typically in %USERPROFILE%\.eclipse\mediniAnalyzeConfig<version>\openWorkspace.

Regards

Jan

Hello Jan,
I have posted the script here.

The script runs perfectly fine when I execute it in Medini. The .docx file is generated
The script is part of the *.mprx file
But when I run it on command line, it doesn't work. I have attached the log for your reference.
I can confirm that the same script is used within Medini and Command Line.

Hi Varma,

I had a quick look and I think the problem is simply how you pass the script name to the CLI. If you want to run a script that is inside of the MPRX, you need to make use of some variables.

It does not work simply by passing a relative path. So instead of:

-s "TestM2DocReports.js"

please try

-s "@project.dir/config/scripts/TestM2DocReports.js"

The @project.dir placeholder is replaced by the real temporary path later by the script handler.

Jan

Btw. the logged exceptions are all fixed in 25.2

already.

Hello Jan,
Upgrading the version to 2025 R2 solves the problem.
Honestly, I didn't know that path to the script should match the one inside the tool. I was exporting the script, and I was trying to run from outside. (I had a hunch that this was wrong)

Two meet my goal of programmatically extracting the consent,

How do I remove the disclaimer, so that there is no manual input needed?
Is it possible to export the data to excel instead of word, so that I can save some effort on the scripting activity?

Varma,

ah, interesting, I was not aware that you had already exported the script to run it from outside. You can do that of course as well but that needs all libraries in place too.

You can export data to Excel (or CSV) for sure using a script, there are several examples out here in the forum how to do that. Those scripts use general purpose Excel libraries and do not rely on m2doc (which is docx only). You may use BIRT for Excel reports but that needs BIRT authoring extensions in medini and maybe some more learning on BIRT.

I will reply separately for the Disclaimer.

Jan

Hello Jan,
Did get a chance to check on how to skip the disclaimer while running the script?