topic Re: write back from front end. in QlikView

write back from front end.

agni_gold — Mon, 25 Apr 2016 13:00:49 GMT

Hi Guys,

I want suggestions from you ,

I am trying to give user as functionality that they can edit data from front end and this will write back to database.

what are the ways to do this.

gwassenaar‌

Re: write back from front end.

robert_mika — Mon, 25 Apr 2016 13:08:33 GMT

One way is to build an extension.

This is possible but required good programming skills.

Feeling Qlikngry?

How To /Missing Manual(25 articles)

Re: write back from front end.

marcus_sommer — Mon, 25 Apr 2016 13:22:52 GMT

Maybe this: SQL Writeback from QlikView extension object. reduced the needed efforts.

- Marcus

Re: write back from front end.

petter — Mon, 25 Apr 2016 14:30:56 GMT

Just to be entirely correct there are actually at least 5 approaches to do a write-back to another system from QlikView (depending on how you categorize them). There is not so much information here on Community on how to do it in a reliable way - with full examples.

Create a QlikView Extension as suggested by Robert. The one that is rather well documented.
URL Action - The URL can be a query-string that is interpreted by another system to contain some data. Limitations to data size.
Invoke a WebService via a VBScript/JScript macro. And yes they can be run from Ajax and on the server contrary to what some people claim on this forum.
Do a ServerSideExportEx() function call via the COM-Object Model for QlikView on the server to store a file. This file can be picked up with a Windows operating system WindowsFileSystemWatcher trigger that reads the file and store the content in another system via database calls or REST-calls or whatever.
Use Varibles that are stored as part of a bookmark and shared between users and have an application reading this bookmark and storing the information into another system.

The level of effort and risk is or could be rather high on any of these approaches. It does require insights into technologies that many QlikView developers might not have. So I have never seen this as recommended practice from Qlik - but it is feasible for some use-cases.

In most cases it would be safer and cheaper to buy third-party solutions to do this. There are several...

Re: write back from front end.

ThornOfCrowns — Mon, 25 Apr 2016 14:37:08 GMT

You're also aware of the huge can of worms you're about to open by giving user(s) read/write functionality to your back end databases, right?

Re: write back from front end.

agni_gold — Mon, 25 Apr 2016 14:57:42 GMT

yes , actually user wants to edit table record.

Re: write back from front end.

petter — Mon, 25 Apr 2016 15:06:44 GMT

James advice is very sound. You should be very reluctant in saying yes to something that might have a huge cost. Implementing this might cost as much as 5 to 20 times as much time as building the regular QlikView application. So don't promise them that is will be a quick and easy extra that they get for free...