topic Re: Triggers on field gets lost in QlikView

Triggers on field gets lost

martinpohl — Wed, 10 Oct 2012 12:38:01 GMT

You can set a action on a field at the triggers in documents settings for example by selecting.

When the field is lost after executing script by an error, the action is lost, too.

Is there a way to set the actions in the script?

Regards

Re: Triggers on field gets lost

hallquist_nate — Wed, 10 Oct 2012 15:41:22 GMT

You lost me on this one. If the field is lost due to an error during a reload, the action won't work no matter where it iss, as the field is lost. Are you just looking to not lose the action, in general, so when you recover the field the action can be used? That sounds like a possible bug. What version of QV are you using and where is the action being lost? IS it on the Access Point, Ajax, or the .QVW file?

More info please...

Nate

Re: Triggers on field gets lost

erichshiino — Wed, 10 Oct 2012 15:53:59 GMT

Hi,

I reproduced the problem on QV 11 SR1.

If in any reload you lose the field with the trigger, it will be lost even when you recover the field.

It is not possible to recreate it on script. Maybe you could write a macro with some effort to recreate the trigger but it would be a problem to use it. I'd suggest you call this macro on post reload method, but this event is not triggered on server reload...

Then, I'd say it is a bug...

Regards,

Erich

Re: Triggers on field gets lost

rwunderlich — Wed, 10 Oct 2012 16:14:50 GMT

An interesting thread. A couple comments.

1) You can't define the Actions with a macro, as there is no API to define Actions.

2) When I get a script error, I click Cancel and reload the old content. Some people click Cancel and press on. This issue - lost Actions -- would appear to be a side effect of clicking OK.

-Rob

Re: Triggers on field gets lost

hallquist_nate — Wed, 10 Oct 2012 16:16:18 GMT

I would also register this bug with QlikTech. I would think that a document "property" should be saved, and not lost, even on a field loss. When you lose a field that is a dimension in a chart, it get the red line, and is not removed. I would think the same behavior should be expected throughout the application.

Re: Triggers on field gets lost

erichshiino — Wed, 10 Oct 2012 16:21:11 GMT

Hi, Rob.

There should be methods to manage actions...

If the code used Load * from or Select * the script could finish without erros killing the actions.

We also need to be careful with 'Exit script' in the middle of the code to test parts of the script because we can potentially lose the actions.

Regards,

Erich

Re: Triggers on field gets lost

hallquist_nate — Wed, 10 Oct 2012 16:32:44 GMT

I'm guessing that there are 1 of 2 things happening to Martin.

1. Martin is still building the app and the load fails, just as a part of the Dev process. The action was in, and now he lost it on the last failure. (We've all been there!)

2. Someone is making unanounced changes to the underlying data structure and causing the failures from QVS.

I'm guessing that scenario 1 is what is happening.

Nate

Re: Triggers on field gets lost

martinpohl — Thu, 11 Oct 2012 06:36:38 GMT

Hello @ all.

Thanks for your suggestions.

The workaround to cancel the script and reload the previous version may working while developing with the client.

If this happens at the reloadjob because a file is corruped or missing you can't stop saving the file with the missing field.

Another workaround I'm thinking about:

load the action fields with an inline load without datas at the beginning so the field will be saved and also the actions.

Regards

Re: Triggers on field gets lost

Tue, 27 Nov 2012 15:17:26 GMT

It's a very poor behaviour, and I would expect these settings to be persisted. Has anyone raised it as a bug (or after you have been told it is "by design", an idea)?

I have just added a dummy table to the start of my load script to ensure these fields always exist - it seems to be working fine for me (when the script errors, or if I use an Exit Script statement during debugging).

Re: Triggers on field gets lost

flipside — Tue, 27 Nov 2012 16:19:20 GMT

Further to earlier posts, it IS possible to create and amend field triggers via macro, but not yet sure if all options are covered.

The following code from APIGuide reads the triggers as set up ...

set fld=ActiveDocument.GetField("Customer")

set fp = fld.GetProperties

set actions=fp.OnLockActionItems

for i=0 to actions.Count-1

msgbox "Action types: " & actions.item(i).Type

next

.. by amending this slightly I have managed to change the order of the actions and add a new one ...

set fld=ActiveDocument.GetField("timeTrigger")

set fp = fld.GetProperties

set actions=fp.OnLockActionItems

msgbox "Action types: " & actions.item(0).Type 'Originally set up as activate next sheet

msgbox "Action types: " & actions.item(1).Type 'Originally set up as activate previous sheet

actions.item(0).Type = 10 'Activate previous sheet

actions.item(1).Type = 9 'Activate next sheet

actions.add

actions.item(2).Type = 10 'New action

fld.SetProperties fp

... might be useful to someone.

flipside

Re: Triggers on field gets lost

erichshiino — Tue, 27 Nov 2012 17:31:43 GMT

Hi,

I created an idea

http://community.qlik.com/ideas/2687

It's still "awaiting review", then it's not possible to vote for it yet...

Interesting workaround

Regards,

Erich

Re: Triggers on field gets lost

Tue, 27 Nov 2012 18:18:19 GMT

Great - thanks for letting me know. I have bookmarked it and will vote when it is approved. Thanks.

Re: Triggers on field gets lost

Fri, 05 Apr 2013 16:57:25 GMT

My personnal solution to manage this problem and having no data lost is :

// True if in dev mode ; flase other
LET vDebug_AutoSave=True();

// SUB for copy file to another one
SUB FILE_COPY (Src,Dest)
trace 'FILE_COPY "$(Src)" "$(Dest)"' ;
EXECUTE cmd.exe /C C: && COPY /Y "$(Src)" "$(Dest)";
ENDSUB

// first line of active code in the main is :
// if can find my version with data + just before any error on the file in date & documentName format
IF (vDebug_AutoSave=True()) then
CALL FILE_COPY (DocumentName(),Timestamp(Now(),' YYYYDDMMhhmmsss')&DocumentName());
ENDIF

Re: Triggers on field gets lost

rwunderlich — Fri, 05 Apr 2013 18:00:52 GMT

Your script seems to duplicate the native functionality available in Settings, User Preferences, Save. Specifically, "Save before reload" and "Use backup instances".

Is there some advantage to the script snippet you posted?

-Rob

Re: Triggers on field gets lost

Sat, 06 Apr 2013 00:21:23 GMT

Y ou're right Rob.

I was not aware of this setting.
(as all ingeneers,i have not read the manual )

I will try your suggestion.

Thanks.

Re: Triggers on field gets lost

magavi_framsteg — Tue, 15 Oct 2013 10:26:04 GMT

Hi Martin.

I am stumbeling upon the same problem at one of my clients, and I am using -prj-folders to hold document definitions.

And they use Git for version control.

The problem arises when we want to use Git to deploy apps.

When docs are recreated using -prj-folders, they get recreated W/O data - that is, no data model and thus no fields.

And NO field event triggers, which are vital for almost all apps I've ever seen, in one way or another.

Anyway, I opened a ticket on QT support right about now.

So maybe it will come in QV 11.2 SR6 😃

Kind regards

Magnus Åvitsland

BI Architect Consultant

Framsteg Business Intelligence Corp.

Re: Triggers on field gets lost

Tue, 01 Apr 2014 10:16:53 GMT

Hi,

I'm facing the same situation when using SVN for transporting the PRJ folder from one machine to another. As this is my company's approach to move a QVW to production, I somehow need to fix this.

Is there a way to store field event triggers to a macro / load script etc. in the meanwhile? I tried to run the script from flipside above, but it does not do anything in my QVW file.

Thanks.

Re: Triggers on field gets lost

Wed, 02 Apr 2014 05:57:44 GMT

Anyone?

Re: Triggers on field gets lost

Thu, 03 Apr 2014 06:38:52 GMT

No solution, but the idea mentioned above in this thread is now live, so for a long term, non "work around" solution - go and vote

http://community.qlik.com/ideas/2687

Thanks

Re: Triggers on field gets lost

Wed, 04 Jun 2014 14:14:54 GMT

Hi Magnus,

We had the same problem when pulling a qvw out of Source Control. A good workaround is to create a script (with Powershell or something similar) that scans through the AllProperties.xml file (in the -prj folder) for the fields that you want to have triggers, and replaces the <OnSelectAction></OnSelectAction> node with one containing the correct syntax for the trigger you're after. For example, if I wanted to add a trigger to run a macro called 'MyMacro', it would look like the following:

<Type>TYPE_MACRO</Type>

<v>MyMacro</v>

</StringExpr>

</Parameters>

</ActionItemDef>

</OnSelectActionItems>

For other types of triggers, the best way to get the xml syntax correct is to recreate the trigger manually in the desktop client, save and exit, then search the xml file for the given field and make a note of how it is displayed.

My script contains a hashtable that pairs each Field name with the required xml that I need to insert. If you keep this updated every time you add a trigger, it should be easy to run and 'repair' your 'AllProperties.xml' if the triggers ever drop in future. Once the xml has had the triggers re-applied, you should find them there next time you open the qvw.

Hope this helps.
-James