Hi Peter!

It's really a great app, I'm using every week to quickly analyze CSVs and make reports.

The question: suppose I built a cube, pivots, and dashboards against the particular CSV file. And then I'm getting the new csv with the same format but different data.

What is my approach to using the data from CSV with what I already built for CSV and to avoid building everything from scratch?

Top 3 most discussed questions are about ObjectScript.

Top viewed questions are about ODBC, JSON, CORS and Excel.

Top 6 voted questions are about @Otto Karlinger and Otto's fan club ) Do you think guys we need to cancel voting for questions?

@Robert Cemper!

Congrats for amazing 142 votes for answers this year! This is a tremendous help to InterSystems Community and maybe an unbeaten record! Thank you so much, Robert, and thank you very much, experts, who solved so many problems and helped developers this year!

@Mark Bolinsky - your article is the most viewed this year! Not surprised )

@Henry Pereira  - congrats on the most voted article - everybody agrees that unit tests are 'the must' but not everybody is using it ;) And voting for this is almost using this! :)

@Henrique Dias - and yours the most discussed, perhaps the monitoring is the hottest topic! Wish we add it to ZPM to make the installation instant.

Thank you, gentlemen! 

And thanks all for contributing such great articles this year!

Hi Peter!

Thanks for the question.

It makes a lot of sense to test your package before publishing it on ZPM-registry.

You can test it via 'load' and 'publish' commands of ZPM-client.

Suppose, you have IRIS with ZPM client installed and you have the repo folder locally with module.xml in the root. Then you can use following command to test the module.xml loading:

USER:zpm>load /yourfolder/withrepo/

or with -v with more details:

USER:zpm>load -v /yourfolder/withrepo/

It shows the log and if module.xml is not correct you'll see errors in the log. This is the test of resources description.

Then you can test the publisher with 'publish' command. Call:

USER:zpm>packagename publish

or with -v with more details:

USER:zpm>packagename publish -v

This will try to execute all the tests, run web-app settings and call invoke methods locally. This will then refuse to publish cause you don't have the registry locally - which is OK, because you don't want to publish locally, right? All other errors will tell you if something is wrong with your module.xml package. 

HTH