Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Ranjanac1
Contributor II
Contributor II

Assistance Required: Identifying QlikView Applications with Macro Functionality

Hi, Good Morning,


I’m currently working on identifying which QlikView applications contain macro functionality. Since there are numerous `.qvw` files, I’ve been using a PowerShell script to scan a specified directory and generate a report indicating whether each file contains macros.

However, the script is not producing the expected results. The output I’m receiving differs significantly from what I anticipated.

- **Expected Output:** Please refer to the attached file `Expected_Sample.txt`.
- **Actual Output:** Located in the folder `Real Output`.
- **Script Used:** Attached for your reference.

Could you please assist me in troubleshooting this issue or suggest a better approach to achieve the desired outcome?

Thank you in advance for your support.

Regards,
Ranjana Chakraborty

2 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I don't know powershell enough to suggest what may be the problem here. What I can do is point you to a couple of utilities where I do something similar, but with VbScript inside QlikView. 

Qlikview Cookbook: Script Repository https://qlikviewcookbook.com/recipes/download-info/script-repository/

This utility processes the qvw files in an input directory and extracts the Load script and Module text to files in the output directory.

Qlikview Cookbook: QV Document Analyzer https://qlikviewcookbook.com/recipes/download-info/document-analyzer/

QV Document analyzer extracts metadata, including Actions, from a QVW. You could copy some code from the QC Doc Analyzer Module that extracts Actions into a copy of the aforementioned Script Repo and record the macro calls along with the module extract. 

I know may be simpler if you could fix the PS script 🙂

-Rob

marcus_sommer

In addition you may look into the APIGuide.qvw to get hints for the available properties and needed syntax as well as various example-code. And like Rob hinted it might be more pragmatic to take the nativ VBS instead of transferring it to PS.

QlikView COM API reference (download QV document)