Share
ReportWe're seeing a strange and inconsistent behavior in two of our Dynamics 365 testing environments with regard to the ODATA endpoints of each environment. We installed the same solutions in both environments but are seeing an identical query gives an error in one environment but is working in the other.
In the query below, pafo_questionnaireresponses is an entity, which has a lookup field on it with schema name pafo_applicationId.
We have two different <sandbox> environments, lets call them SB1 and SB2.
In SB1, the query gives us an error:
"Could not find a property named 'pafo_applicationId' on type 'Microsoft.Dynamics.CRM.pafo_questionnaireresponse'."
But if we change the expand to be all lowercase, so that it reads $expand=pafo_applicationid, the query works and returns results.
Meanwhile in SB2 the original query gives us results but if we change it to all lowercase here, we get this error:
"Could not find a property named 'pafo_applicationid' on type 'Microsoft.Dynamics.CRM.pafo_questionnaireresponse'."
I have confirmed that both environments' solutions are the same versions and if I look at the entity in the customizations the schema name is identical.
Looking at the CRM versions of the two environments:
SB1: Version 1612 (8.2.1.344) (DB 8.2.1.341) online
SB2: Version 1612 (8.2.1.344) (DB 8.2.1.344) online
Could the DB discrepancy be the cause of this issue? Or is there some other intricacy of the ODATA endpoint that we are missing?
*This post is locked for comments
All responses (
Answers (
291,269
