Access Dynamics CRM via SSIS OData: estimatedclosedate null

(0) Share

Report

Posted on by Ivan_Arribas

Hi all,

I'm developing a SSIS solution to import Opportunities data to a OLAP Cube via SQL 2016 SSIS new Odata for Dynamics CRM online.

All Works fine, except that the 'estimatedclosedate' and 'actualclosedate' fields are NULL but they are informed in CRM.

There is not problema with other date fieldas like 'modifiedon' or 'createdon'.

Any idea?

Regards!

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

TomSmelser 1,570 on at

Like (0)

Report

Ivan,

Not certain how to fix this. But I see these fields can be defined with Behavior and Format as "Date Only" in CRM. This affects time zone handling. Not sure that is the issue. But you could experiment by creating a 2nd "actualclosedateForExport" as Date/Time and create a workflow to copy actualclosedate to it. Then try your export to see if it appears. A bit of work, but at least may give you clues and a workaround.

Good luck!

Tom

Was this reply helpful? Yes No
Ivan_Arribas 5 on at

Like (0)

Report

Hi,

It's a great workaround in order to solve the issue. The problem is that I'm working in a BI solution, but I have no access to the CRM solution development. I need to solve the issue without CRM development,

Regards,

Was this reply helpful? Yes No
Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

Hello Ivan,

Mentioned fields are stored in opportunityclose entity. To get it you will have to make a join from opportunity to opportunityclose. Good luck.

Was this reply helpful? Yes No
Ivan_Arribas 5 on at

Like (0)

Report

The problem is not with the entity, both fields are in opportunity entity.

The problem is that "actualclosedate" and "estimatedclosedate" are datetime fields, but with a "Date Only" behaviour, so SSIS Odata source expect a DateTime field but only receives a Date.

Need help!!

Was this reply helpful? Yes No
gaupop-4423 15 on at

Like (0)

Report

Hi Ivan, did you get to solve this issue? I am currently facing a similar issue with fetching date field from Odata url to SSIS. Could you please share if you have any insights?

Was this reply helpful? Yes No