Some of the schema collections (returned when calling GetSchema() method on the CrmAdo db connection object) are not quite aligned with Sql Servers in terms of the restrictions they have, and the ordering of the columns they return.
Let's try to make these as close as possible.
The primary reason for this is that the Ddex provider is currently hitting problems when displaying the standard Query Designer in visual studio (to visually build a query) and the issue there is that irrespective of which columns you pick, the designer executes a command to select all columns!
It's not possible to debug the designer code to see the cause of the issue. However the designer must be metadata driven, and so one angle of attack is to make sure metadata returned is as close as possible to what SQL servers would return - just in case its a meta data issue.
Hoping this will solve the issue with the query designer, but if it doesn't then we know its not anything to do with the Crm Ado.net provider's metadata at least.
Some of the schema collections (returned when calling
GetSchema()method on the CrmAdo db connection object) are not quite aligned with Sql Servers in terms of the restrictions they have, and the ordering of the columns they return.Let's try to make these as close as possible. The primary reason for this is that the Ddex provider is currently hitting problems when displaying the standard Query Designer in visual studio (to visually build a query) and the issue there is that irrespective of which columns you pick, the designer executes a command to select all columns!
It's not possible to debug the designer code to see the cause of the issue. However the designer must be metadata driven, and so one angle of attack is to make sure metadata returned is as close as possible to what SQL servers would return - just in case its a meta data issue. Hoping this will solve the issue with the query designer, but if it doesn't then we know its not anything to do with the Crm Ado.net provider's metadata at least.