Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Facing an error while importing data from Salesforce CRM

Avatar

Avatar
Validate 1
Level 1
somasundaramb
Level 1

Likes

0 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
somasundaramb
Level 1

Likes

0 likes

Total Posts

3 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
somasundaramb
Level 1

18-02-2021

Hello Experts, 

We've connected one of our sandbox into dev instance by using Salesforce CRM connector external account. The connection is successfully configured and we could able to see the remote object in the data import workflow 

 

The problem is, when i try to pull data from crm with ID as record identififer, I'm getting the following error 

 

02/18/2021 11:52:55 AM crmConnectorDataMgt Unable to parse remote time '2021-02-18T17:52:55.399Z'. Cause 'Could not find out the remote date and time. Cannot compute the time difference between the CRM and Adobe Campaign.'.

 

I just checked the LastModifiedDate format with CRM and it seems different. so we tried to do the data type conversion in the CRM connector and it is not working as well. Created a Option and tried to pull data with "Use Automatic Index", again the same error is appearing

 

It would be really helpful if any one can help us. Or it would be helpful if you can share the best practice or mandatory things to consider while importing data from salesforce CRM

 

Thanks

Soma

Adobe Campaign Classic Salesforce CRM

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

155 likes

Total Posts

239 posts

Correct Reply

141 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

155 likes

Total Posts

239 posts

Correct Reply

141 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
craigthonis
Employee

19-02-2021

Hello,

 

This error seems that it's a bug (NEO-17712) in the connector.  Please make sure you upgrade to the latest version of as I am seeing fixes in the latest release for this.

 

Regards,

Craig

Answers (0)