QV 12.3 SR2 - macro not working - Qlik Community

shane_spencer · ‎2019-09-12

Has anyone noticed that macros are not working in QV 12.3 SR2 desktop version? We've developed many apps in QV 12.1 SR7 that require the use of macros. Just tried using the same tools at a client site and the macros are not working on their pc's. When they uninstalled and installed the earlier version they worked.

n.b. attached a simple qvw with a ZOOM macro for testing.

Brett_Bleess · ‎2019-09-25

Hey Shane, I just tested things in 12.40 SR1, and I have to click the text object, which is working as expected I believe. I also created a button object, and that worked too, but I did have to click the text object to get the macro to run, and that makes sense in this case, as there is no other means for things to be triggered. The only other thing you could do here is use Doc Props and OnOpen trigger to run the macro that way, but that will be unsupported in Ajax Client, just FYI. You will likely have to use a note on the object or a button the users can click to set the sizing that way etc., best workaround I have here. If you find documentation that states this should be working differently, then I would say you can go ahead and open a support case at that point, but from what I can tell currently, things are working as expected.

Here is the key statement from the Help on the text object as well: https://help.qlik.com/en-US/qlikview/November2018/Subsystems/Client/Content/QV_QlikView/Text%20Objec...

"In the Actions tab you can specify what actions should be performed when you click on the object. The page is identical to the Actions page for the button object."

The object has to be clicked to activate the Action... If 12.30 SR2 is not behaving the same way, test the SR3 release to be sure that still has the issue as well. Shout if you have questions.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.

shane_spencer · ‎2019-09-25

Hi Brett - thanks for your reply.

Currently we use QV 12.1 SR7 Desktop as it's the latest version we know to not have bugs that affect our tools.

However our clients often already have a version of QV installed, and they are often reluctant to change versions especially if they already have a later version.

Hence why I was specifically asking about QV12.3 SR2 desktop.

If you're saying that 12.4 SR1 is working then that's something at least. If I had the time I would test all recent versions but we've got so much functionality in our tools that just because macros works in a version there's not saying something like inline loads will also work (which is something I have seen in some versions too).

Brett_Bleess · ‎2019-09-25

Shane, here is a link that is pertinent to having folks on the latest SRs in the major tracks, security vulnerability....

https://community.qlik.com/t5/Qlik-Support-Updates-Blog/QlikView-and-Qlik-Sense-Important-Security-F...

Hopefully that may get many of them to update to the latest SR within their tracks.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.

shane_spencer · ‎2019-09-25

Hi Brett, the trouble is when we find bugs in later versions we don't want the client on the latest but on a specific version that we know works with our tools. Thanks, Shane.

Brett_Bleess · ‎2019-09-25

Shane, allowing customers to run on releases that have security vulnerabilities is not something I would recommend either... As a prior CISA, this is something I would have flagged when doing IT audits of said environments... Just making my point that that is more to this, this vulnerability should not be ignored.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.

shane_spencer · ‎2019-09-25

I understand your point, but it's a bit like advising that I should travel to work in a tank even though it doesn't actually run rather than my car because it's more secure.

marcus_sommer · ‎2019-09-25

Did it happens to all macros and all triggers or only to certain ones? Means, are simple things like: msgbox "hello world" running or not?

Did you try the macros on the users machine - in the UI and in the module editor? Give err.number and err.description any hints?

Were the security settings within the modul editor and in the user-properties checked?

- Marcus

shane_spencer · ‎2019-09-25

None worked. Even simple ones. All setting were enabled.

Uninstalled QV. Installed QV 12.1 SR7 and they worked.

marcus_sommer · ‎2019-09-25

I assume there are changes in the settings. I think I would compare the settings.ini of both installations - especially settings like MacroLaunchConfirmation or the various Override-Settings.

- Marcus