Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Contributor III

QMSEDX for V12

Does anyone have a link for the latest version? The only link I've found (which points to Doc-5111 I think) no longer works.

Tags (1)
3 Replies

Re: QMSEDX for V12

Try this one

Using EDX in QlikView 11


Contributor III

Re: QMSEDX for V12

Thanks Rob. I had that information already, as it appears to still be the original version of QMSEDX. There was a newer release, called QMSEDX Enhanced, that was in a doc here in community called DOC-5111, but that seems to have been deleted.

However, I don't think I need it now. After fixing a certificates problem on our server after upgrading from 11.2 to 12.1 this past weekend, the QMSEDX implementation originally set up several years ago is now working. Go figure. But I did get the following response from Tech Support, which I guess I don't need to do now, in case anyone else searches community on this issue.


There have been some changes to how this functionality works in the later versions of QlikView.  This information is also found in the release notes, that are linked at the bottom of the page.

The QMS API has changed. As a result, the URL version suffix is now 12 and will affect all programs developed using previous versions of the QMS API.  To update a program developed in Visual Studio, do the following:

1. Right-click Service Reference, and then select QMSAPI.

2. Select Configure Service Reference and make sure the Address is pointing to your QMS. For example, http://computername:4799/QMS/Service

3. Right-click Service Reference, and then select QMSAPI.

4. Select Update Service Reference.

Recompile to update the program. If additional issues occur, make sure that nothing in the project points to version 11.


Re: QMSEDX for V12

Glad it's working. I should have pointed out that what I meant was the last version works fine on V12


Community Browser