Error connecting QlikView to Facebook with REST Connector and Pagination

[#1]

Enter by mto‌ on behalf of piersbatchelor‌

We are receiving the following error when using QlikView and the REST Connector 1.0 and 1.1 - when accessing Facebook using the Graph API.

IsNextUrlFieldPathHeader has no value, or misplaced semicolon

The error only occurs when we click the select button after we configured the REST Connector UI use the pagination parameter:

Next URL: root/paging/next

It seems this occurs because an empty parameter is created in the CONNECT String because the header checkbox is NOT checked and we get:

NextUrlFieldPath=root/paging/next;IsNextUrlFieldPathHeader;

If I remove the field - we can get data and pagination works, but the select button keeps yielding the same error.

[Michael_Tarallo · Accepted solution]

Hello Piers,

Hi Piers - thanks for helping me discover more on the WebEx - please see the notes below for our reference.

Potential bug in REST Connector 1.0 and 1.1 when using pagination with Facebook, causing the select interface to fail when using QlikView and the REST Connector.

Workaround:

• use the REST UI to configure your connection WITHOUT the pagination parameter selected
• select your fields/nodes/values with the select interface
• manually edit the CONNECT string and ADD the parameters such as PaginationType=NextUrl;NextUrlFieldPath=root/paging/next; parameter
• your data should load with pagination

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

Regards,

Michael Tarallo (@mtarallo) | Twitter

Qlik

[#3]

Hi Michael

I've been working with the REST connector and get the same error. Before I get a 3rd party consultant in to help, do you know if there has been any updates?

I have tried to manually enter the snippet that you shared, but am still only getting the 25 or getting the initial error that Piers was getting.

Any ideas at all?

With thanks,

Simon

[Michael_Tarallo]

Hi Simon - can you paste the connect string you are using? I will check with the PM on this.

Thanks

Mike

[#5]

Hi Michael,

Thanks for the quick reply, the access token might not work for you, but below is the string that I'm using:

CUSTOM CONNECT TO "Provider=QvRestConnector.exe;url=https://graph.facebook.com/v2.10/126761694007536?fields%2posts

&access_token%2EAACEdEose0cBAEpJ9v5lFZCVgvdS14BKPuLZBvoxywO7AJhIEnPWqeeBBZCTgGMbpMAZCfFoxSUWKkWCDCexaEktsNTBVI67d9VMH8ou5JZC4LwufGaN72SPHYT9rUrw3gsALdqllJZAOqwbkHt0t3PZBkgwqkTe0MdmPBUSZAtYM7MuTyZCrlR0qQ9DPk3gSX9LImYS0qkKUSTXK6gY6M1ME;

timeout=30;method=GET;autoDetectResponseType=true;keyGenerationStrategy=0;useWindowsAuthentication=false;useCertificate=No;certificateStoreLocation=CurrentUser;certificateStoreName=My;

PaginationType=NextUrl;NextUrlFieldPath=root/paging/next;";

Thank you,

Simon

[Michael_Tarallo]

can you send me a new access token - I'd like to try on my side - thanks

[#7]

Thanks again for your help Michael,

Below is the token that we are using, it is still limited to 25 posts.

LET vACCESS_TOKEN = 'EAADMskzZBqQEBAKAaqu1UB6LcjFUcDvM5C7XCWZCcqJbulyKuEdZAJfwtV9K1PztUJIY8Hz2VAY5sq6LZC4nZBTGpvkLJZCTjxSAS27jdjZCkB5IUgvhrllChaCS4FR1WmzxduOiLJMNThQ9v4K6uJqZArywEh4mxe4OrjCBwJpDpUKciCl37eTd';

CUSTOM CONNECT TO "Provider=QvRestConnector.exe;url=https://graph.facebook.com/v2.10/samsunguk?fields%2posts&access_token%2$(vACCESS_TOKEN);timeout=30;m...";

[Michael_Tarallo]

Hello Simon - there is still a major bug in this REST interface in QlikView as per this discussion - so I had to setup the connection like this to grab the fields using the select button:

I tried NEXT URL and Next token and still only get 25 records - I assume there are more correct?

Note your paging is root/posts/paging/next

I have sent this to our PM daz‌ - am still waiting to hear from him.

Thanks for your patience.

I will still try a few more things - if I have any success I will let you know.

[murugesh]

Team,

I am also facing the same issue, Could you help me out.