Extension object and input fields

[celindho]

Hi,

I am creating an extension object for manipulating input field values. I have not found any specific documentation on the API that would allow me to interact with the input fields over AJAX. Is it possible to build an extension object that would manipulate the input field values (assuming that my chart expression is built using the inputsum aggregation function)?

BR,

-Christian

[Alexander_Thor]

You can interact with variables but I'm guessing you want to write back data into the QV data model.

Atleast that usually is the requirment when people start fiddeling around with input fields

Afaik you are not able to write back data into the QV data model through the JSApi.

[christian77]

Hi:

Input fields are very limited. They're just for a view.

If you want to modify a QV table, use VB in the macro module.

Use variables to set up your entry values.

Open de API Guide, (documentation) and look for UPDATE. It'll show you the sintax for that.

Then, check the next:

[christian77]

changing pics when re-editing does not work

[celindho]

Thanks for the reply.

I was thinking that since the normal table box can do the write back (via AJAX), I could use the same API calls in my extension. But apparently this is not possible?

-Christian

[Alexander_Thor]

Well, you can execute a macro that performs insert/update/delete statements in the ajax-client. That would invoke a cache flush.

I would approach this very carefully. Usually people want to build budget/planning solutions and then opt to work with input fields instead of introducing a data store into the mix.

This has seen some success in smaller user numbers and limited complexity to the process. But it wont scale very nicely for you as you encounter a more complex process with several process flows and check points.

Edit: You need to allow dynamic data update in QMC aswell, System -> Setup -> QlikView Servers -> Security

[celindho]

Thanks for your replies. I have now come to the conclusion that the easiest way to improve on the input field functionality, is to reskin and add some minor functionality to the normal straigth table or pivot table. This would allow me to retain all the functionality that already is embedded in the standard QlikView objects.