topic Re: Qlik Salesforce connector timestamp error in Connectivity & Data Prep

Qlik Salesforce connector timestamp error

kundan_ghosh — Mon, 22 Jan 2018 10:28:28 GMT

I am pulling in data from Salesforce Veeva CRM using native connector in Qlik Sense and I am getting problem with timestamp.

Salesforce saves the value as 16/10/17 but when I extract it into Qlik Sense, it is saving it as 43023.xxx -> the integer part of this value means 15/10/17. However, in other cases, when the timestamp is not near midnight, Qlik Sense saves the values correctly.

I was able to use the following transformation to fix the dates:

Date(Round(Date_vod__c,1))

But I would like to know why is Qlik not able to correctly extract the timestamps. Does Salesforce has a different logic of storing timestamp or is this a bug in Qlik Salesforce connector

Re: Qlik Salesforce connector timestamp error

Anonymous — Mon, 12 Feb 2018 21:56:32 GMT

I believe I hit the same problem, some dates in Qlik Sense are 1 day behind the values in SFDC.

But how did you get to see the actual value 43023.xxx stored in Qlik Sense?

Where do you apply the transformation Date(Round(Date_vod__c,1)) ? In Data Manager?

Re: Qlik Salesforce connector timestamp error

Anonymous — Tue, 13 Feb 2018 08:44:03 GMT

kundan_ghosh‌ I think the answer is here: Create a Salesforce connection ‒ Qlik Connectors

If Convert UTC to local time is not selected, the connector returns date-time values from Salesforce.com in Coordinated Universal Time (UTC).

To align dates displayed in SFDC with those in Qlik Sense output, the option Convert UTC to local time in the connector set-up needs to be selected

Re: Qlik Salesforce connector timestamp error

kundan_ghosh — Wed, 14 Feb 2018 02:55:07 GMT

Thanks for responding to my original query.

(1) I used Rob Wunderlich's free tool QViewer (http://easyqlik.com/) to look inside the QVD

(2) I do not use the Data Manager (primarily meant for self-service users). I used the transformation in load script

Re: Qlik Salesforce connector timestamp error

Anonymous — Wed, 14 Feb 2018 07:25:24 GMT

Thanks for sharing your approach