Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Aug 12, 2024 3:49:13 AM
Aug 12, 2024 3:49:13 AM
This article documents the use case scenario of using CVENT Core.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
Qlik has used CVENT Core to organize sessions for Qlik Connect, allowing Qlik to extract data hourly into a Qlik Sense app.
Cvent Core uses 2-legged oAuth2. Qlik Application Automation's oAuth2 connectors currently only support 3-legged oAuth2, so I had to work around by connecting straight to Qlik Sense REST Connector, where we could do 2-legged. Here's how we did this.
// Get access token using Basic Auth
LIB CONNECT TO 'QlikWorld:CVENT_TOKENREFRESH';
TokenRaw:
SQL SELECT
"access_token"
FROM JSON (wrap on) "root";
[Token]:
LOAD [access_token]
RESIDENT TokenRaw;
DROP TABLE TokenRaw;
let vAuthToken=peek('access_token',-1);
drop table Token;
//Trace $(vAuthToken);
FROM JSON (wrap on) "root" PK "__KEY_root"
WITH CONNECTION (
HTTPHEADER "Authorization" "Bearer $(vAuthToken)"
);