Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a qv document with Rapahel_Integration_Extension and can be accessed via QV Server Accesspoint without any problem.
When I add the extension object into a ASP.NET page, it shows only a blank. Other components (List boxes, labels etc.) in the page shows correctly. Has anyone of you experienced this? ( We are using QV Server 11, Workbench 11 and VS2010 with framework 3.5)
Thanks in advance.
By adding the qv server path (the ip in our case) to the Qva.LoadScript resolved the problem.
i.e. Qva.LoadScript("//<serverip>/QvAjaxZfc/QvsViewClient.aspx?public=only&name=Extensions/raphael_integration/raphael.js",....
Hi.
My wild guess is that the ASP.NET page does not accept the ajax client to be loading the QVW, and instead the IE plugin is loading the QVW. Qlikview Extensions only work with the Ajax client.
If this is not the case - if you are sure that the QVW is loedad in the Ajax client - I have two extensions that I use for testing functionality. See if any of theese work in your environment:
Extension 1: Simple Clickable Example: A simple Example of some clickable boxes. Testing that the Raphael Engine works.
Extension 2: Simple Test: A simple test that extension functionalty works. (No vector integration, only a simple HTML page)
Good luck testing!
Robert Svebeck
Hello Robert.
It looks like we're in a tangled web of Authentication torment! (QV & IIS).
Thanks very much for your examples, it helped us get closer... Right now:
SimpleClickableExample loads and displays fine, provided website is hosted within IIS on the same physical machine as QVS.
When I run the same website hosted on my local dev machine IIS, SimpleClickableExample loads, but the count(F2) box is completely blank.
Have you any other wild guesses??
Thanks again, very much appreciate your time.
Jag kommer att vara borta från kontoret fr.o.m. 2012-05-27 och kommer inte
tillbaka förrän 2012-06-01.
Jag kommer att svara på meddelandet när jag kommer tillbaka.
Have sorted the above issue out.
By adding the qv server path (the ip in our case) to the Qva.LoadScript resolved the problem.
i.e. Qva.LoadScript("//<serverip>/QvAjaxZfc/QvsViewClient.aspx?public=only&name=Extensions/raphael_integration/raphael.js",....