This would allow them to post to our API via Qlik! So I think I have two questions:
1) How to make a text input box within a qlik sense table OR if this is not possible I think I'll just have to use hypercube to build an html table that would have an input box.
2) How to use the Qlik API to pull contents from that specific row in the Qlik table into a POST json. Again if this is not possible I'll have to go from the ground-up to build a html table.
No, the data variable contains the row-data for the current input field (should've probably named the variable on line 14 rowData in the first place ).
You can see the content of the data variable in the screenshot just below the code snippet. Thats the output of the "console.log" statement on line 53.
"FIELD NAME1 OR COLUMN HEADER1": "VALUE OF COLUMN1",
"FIELD NAME2 OR COLUMN HEADER2": "VALUE OF COLUMN2",
Line 34 to 41 are appending a <td> element containing the input field after the last data column and line 44 uses the jQuery .data method to append custom data to an html element (think of data-blabla attributes).
Line 47-54 assigns an event handler for the changed event (will be triggered after you tab out of the textbox), extracts the object that was set in line 44 and creates a property "inputValue" with the <input>-elements current value.
So the data variable contains probably everything you want to send to your REST API.
Thanks so much! I was able to replicate it on a mash-up. I see the text box and I can type in it. I'm noticing some strange behavior that maybe was expected but it's saying: 'Uncaught TypeError: Cannot read property 'dataColIx' of undefined' whenever I highlight the text within the text box - for each character of the text box.
Thanks again for building this out m.schindler I have one more issue that you may be able to resolve pretty quickly. The hards part may be just demonstrating what the problem is haha. When I type in text and then scroll the text in each box stays in there as I scroll. Does that make sense? Please see screen shots.
that happens because Qlik Sense creates a fixed amount of rows whose cell values are just switched out while scrolling. I played around a little bit but could not find an easy solution / workaround for this.
I think you're better off creating your own table extension. Maybe check out this link: