yesterday we upgraded our d365 v8.x to v9.x, after that all of our web APIs calls failing.
it's throwing the following error.
A resource with type 'Microsoft.Dynamics.CRM.incident' was found, but it is not assignable to the expected type 'Microsoft.Dynamics.CRM.customentity'. The type specified in the resource must be equal to either the expected type or a derived type.
I am using d365 web API with OData and this error is coming when we are trying to execute fetchxml using webapi.
Related
We have a case where we need to retrieve sharePoint Document details for particular record in Microsoft CRM, we need exactly two information from the record which are the filename and regardingobjectid (to whom this document belongs to).
I found this post:
https://mscrm16tech.com/2020/09/09/get-sharepoint-document-details-for-particular-record-in-ms-crm-using-fetchxml/
I followed the same approch and i used the fetchXML in c# console program it worked as expected but the probleme when I created an API in azure APIM which will communicate with dynamics to get the results of the fetchXML, here is the policy that I have created:
When I test the API I get this error message (statuscode 500)
NOTE: I checked the URL in the browser (with the same fetchXML) and it worked without a problem also the authorization token was added successfully! also I get the same problem when I tested it in Postman.
What is the problem? I really don't know what to do here, any help will be appreciated.
The issue actually is regarding PowerAutomate (Web version). I am trying to create a custom Github connector as the existing one lacks multiple actions that was needed for my workflow. I setup a simple Get organisation teams API and when I test this action in the builder interface of custom
connector, it works like a charm!!
However when I try to use the same action in a Flow, I encounter the following error:
'The API operation 'GetOrganizationTeams' requires the property 'body/0/parent' to be of type 'String' but is of type 'Object'.
The API documentation for Get Teams can be found here. It is a simple GET request so I don't really know why is the body parameter expected during the API operation.
I tried editing it through the Swagger docs as well, but every time it is returning the same error. Can someone guide me as to what is the exact issue and how can I resolve it?
I'm building a Typescript client that should be able to talk to multiple version of an API.
For example, there is a type User and there are 2 version: v0.1 and v0.2. In version v0.2 there is a new field on the User type called address.
As a a client of the API, I want to query the User type, but use the same query to talk to both version of the API. What I expect is that API v0.1 will return null for this new property.
Is there a way to do this? At the moment I getting this error:
GraphQL error: Field 'address' doesn't exist on type 'User'
If it's not possible, does that mean that for every change to the API, if a client would like to be backward compatible, it needs to store different schema for each version?
I created a simple Bot and its working fine in bot emulator.
I published this Bot into Microsoft azure and trying to registering my Bot with the Microsoft Bot Framework.
I am getting the following error.
object reference not set to an instance of an object.
Can anyone please help ?
According to this issue: https://github.com/Microsoft/BotBuilder/issues/1012 This error can occur if you do not put a url in the terms of use form field.
I'm working with a CRM 4 server. I created a simple console application and added a web service reference to it using the service that resides at http:///mscrmservices/2007/crmservice.asmx?WSDL
Now, according to the SDK, the service's Retrieve method should return BusinessEntity and RerieveMultiple should return BusinessEntityCollection. However, in the proxy that is created on my project, these methods return XmlElement...
What's the problem? what am I doing wrong?
Thanks!
To solve this problem I actually had to use the CRM SDK dlls and connect to the service via them. Adding a web reference didn't work as expected no matter what I tried.