ODBC Dynamics 365 missing Fields

[ptpr0p]

Hi!
When comparing the CRM fields and the fields returned by the ODBC from DEVART and comparing it to DB direct access, I verified that all the fields returned are the same with the exception of the “ownerid$type” field. However, the following fields are missing:

, createdbyyominame
, createdbyname
, createdonbehalfbyyominame
, createdonbehalfbyname
, modifiedbyyominame
, modifiedbyname
,modifiedonbehalfbyyominame
, modifiedonbehalfbyname
, owneridyominame
, owneridname
, owningbusinessunitname

Anyone has experienced this?

Any Fixes?

[Dougal]

Hi, I'm experiencing a similar problem - did you find an answer?

When I run a query against a Dynamics table directly in Sql Server Management Studio, with a 'select *', I get the various '...name' fields you mention.

But running it with the Devart ODBC driver in a Linked Server, these fields are not available.

Sometimes, when the 'name' fields are missing, the non-name equivalents have the 'name' content - eg:

• (direct connection) statecode: 1, statecodename: "completed"
  (devart) statecode: "completed", statecodename: [not a column]

But other times, they do not, eg:

• (direct connection) ps_caseid: "754974E0-F....", ps_caseidname: "person name - Policy - Oct 29 2018"
  (devart) ps_caseid: "754974E0-F....", ps_caseidname: [not a column]

One other oddity is that, via ODBC, the "TOP" clause is not always respected. So if I do:

• SELECT TOP 100 * FROM [DynamicsCrmLive]...[some table];

...I may get in excess of 100 rows, but then when I try:

• SELECT TOP 100 * FROM [DynamicsCrmLive]...[some table] ORDER BY something;

...I'll get exactly 100 rows!

So it's all rather perplexing at the moment - we're in our trial period, so not sure we'll be buying this unless we can work around these problems....