I am using SSIS to connect to Microsoft Dynamics 365(Version 9.0) WebApi to read the data. Below are the details.
Control Name / Transformation(Source Component): OData Source
OData Connection Manager:
Service Document Location: https://organizationname.api.crm4.dynamics.com/api/data/v9.0
Authentication: Microsoft Dynamics CRM Online (with username and password)
After I entered above details and click "Test Connection", the connection is successful.
Now, when I dragged the OData Source Component and selected the OData connection, I am getting below error.
Unable to load the collection for the connection OData source. The connection cannot open
Any pointers on how to fix this error?
Check your service document location. This is the format we had to use to get it work:
https:// [Your organization's root URL]/data
Here's a link to Microsoft D365 and oData that was helpful on a similar project I worked on:
https://learn.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/data-entities/odata
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.
We and our customers are using Dynamics CRM online and DocuSign integration.
Since the last 10 days our customers are receiving an issue in the GetSignatures workflow step.
The error message is:
DocuSign.DSIntegrationActivity.GetSignatures: System.Exception: Unable to deserialize the returned JSON. Endpoint: GetSignatures.
Error Description: Error checking sharepoint folder for /Opportunity (Unknown) Server Response
{"Error":"Unknown","ErrorDescription":"Error checking sharepoint folder for /Opportunity"}
Our customer has the DocuSign integration solution version 6.2.2.0
Can you please help us to solve the issue?
Thank you
This related to your SharePoint mapping either having been changed or Document Management being setup wrong. You need to go through the process described in this article.
Our customers reported that the issue has been solved.
No update or change is required in Dynamics CRM to fix the issue.
DocuSign fixed the issue on the DocuSign side.
I need your help in order to install DocuSign in my Dynamics 365, please.
I am trying to install and configure a DocuSign trial in my Dynamics 365 Demo and I am facing a lot of errors and I can’t finish it.
First of all, I created a new Trial in Docusign Platform
After that, I installed the DocuSign application in my Tenant:
After all of this, I logged in Dynamics 365 using Admin user and I can see the following strange processes in our Dynamics. Could you tell us what these processes are referring to?
On the other hand, I am trying to configure in DocuSign Admin Section > Settings and I face the following error when I try to enable the “Save completed documents to SharePoint” option:
I select the second option:
And the following error is facing: this is the url. Embedded in the url is a stack trace which includes the message:
A potentially dangeraus Request.QueryString value was detected from the Client
I can’t also enable entities:
Please, could you help me?
I have created a simple OData enabled Web Api. Now I want to use this feed from Excel, which seems to require a .svc file of a certain format (that describes the available resources).
Is there something in the ASP.NET Web Api OData library that helps here or do I need to create this myself?
Can any one point me to a example of a Web API OData feed that Excel can consume?
Connect to an OData feed from Excel
In the POWER QUERY ribbon tab, click From Other Source > From OData
Feed.
In the OData Feed dialog box, enter the URL for an OData feed.
Click OK.
If the OData feed requires user credentials, in the Access an OData feed dialog box:
Click Basic if the OData feed requires your username and password.
Click Feed Key if the OData feed requires an account key. You can click the Get your Marketplace Account Key to subscribe to Windows Azure marketplace OData feeds. You can also Sign up for Windows Azure Marketplace from the Access an OData Feed dialog box.
Click Microsoft Online Service ID if the OData feed requires federated access credentials. For Windows Live ID, log into your account.
Click Save.
Source: http://office.microsoft.com/en-us/excel-help/connect-to-an-odata-feed-HA104019824.aspx
Microsoft has changed the authentication model for new CRM sites from LiveID to Microsoft Online Services. I set up a new site this week and have it up and running but code I wrote that connects to the site using early bound classes fails to authenticate.
My connection string for an older site using LiveIDs looks like this.
I am trying to connect to the new site that uses Microsoft Online Services for authentication with this connection string
I create an instance of XrmDataContext and it seems to work OK until I actually upll data fromthe site. The error I receive is
ACS10002: An error occurred while processing the SOAP body. ACS50012: Authentication failed.
I tried all of the authentication types list here http://technet.microsoft.com/en-us/library/ff681567 and none seemed to work.
I see a lot of forum posts saying that the discovery service URL has changed so I tried adding that to my connection string.
Discovery URL=https://disco.crm.dynamics.com/XRMServices/2011/Discovery.svc
No luck.
Has anyone written code that connects to the new security model? Did you do anything special?
Thanks in advance,
Bill Wolohan
MS released a new version of the SDK on 8/17/2012. I had downloaded the latest on 8/16/2012 and that version did not work. Once I downloaded the newer version and recompiled it worked great. I just had bad timing. :-(