I use Microsoft Dynamics CRM 365 and the DocuSign Integration for Dynamics 365 version 5.
My problem is that I can't enable any entities in the DocuSign Admin page in Dynamics.
When I save and refresh the page the previous chosen entities are not selected.
Thanks for help
I compared an other Dynamics demo org and figured out the reason for the issue.
Found the required info in the plugin trace logs.
My Dynamics org was created with the base language german.
The DocuSign integration needs checks if the user has a role with name "system administrator" and in my case the name of system admin role is in german.
And the langue package english should be installed on your Dynamics org.
After that I could enable the entities on the DocuSig Admin page.
Related
When creating users in Dynamics 365 using the Microsoft CRM SDK, the salesperson security role is automatically assigned. We believe this behavior started recently.
It does not happen when creating users in Dynamics 365 using the UI.
The behavior is documented here for imported user.
The security role can also be added automatically based on assigned license. It is possible to opt out of this. One of our customers had Microsoft do this for their Dynamics environment, but the salesperson role is still added automatically.
This does not happen when creating users in on-premises CRM using the same code. There must be something on the Microsoft Dynamics 365 server side adding this security role.
Is there a way to avoid the automatic security role assignment?
We have a workaround by adding the user to the AAD security group of the Dynamics environment and waiting until the synchronization from AAD to Dynamics 365 creates the user before we add access and update personalia/settings using the API.
We have a scenario where we do not have enough licenses to provide to the users for Dynamics CRM Online. But we need these users to be able to edit/create rows in Appointments and Task tables. We have a license with Admin access. Can this license be shared or used in such a way that users can edit these tables through any other interface say using Power Apps or so? Is there any way to enable them to edit the tables?
What you can do is, get the per-user-per-app license for users so they can use Canvas app and get authenticated using AD SSO.
You can use the Admin service account to do data interactions into Dynamics CRM using MS Flow/Power Automate. Essentially CDS connector will use the licensed CRM admin account in the backend. Honestly I never tried this.
Another user also used HTTP request to use LogicApps to POST the data without license. Reference
PowerApps portals is another option.
The documentation isn't clear on how to register your application to access the Office 365 outlook REST API. The documentation seems to say to go to the Microsoft Application Registration Portal, but logging in with 3 different accounts fails.
In order to use the Application Registration Portal, you need either an Office 365 work or school account, or a Microsoft account. If you don't have either of these, you have a number of options:
While you can use any Microsoft account to register applications, in order to access mail/calendar/contacts you need an upgraded Outlook.com account with the REST APIs enabled. To get an upgraded Outlook.com account, you could click here for solutions
obtain an Office 365 subscription ,also refer to above link for details.
If you register App in Microsoft Application Registration Portal, the app only support V2 authentication endpoints.
Another choice is to register your app with Azure AD ,so your application could use the OAuth2 Client Credentials Grant Flow, or need to access other Office 365 workloads besides Outlook (such as OneDrive for Business or SharePoint).
This article includes detail steps about manually register your app with Azure AD so it can access Office 365 APIs .
I am attempting to create a simple application for creating users in our on-prem Dynamics 2013 CRM installation. Right now, we create a user in AD then go to CRM and import the user by entering the AD username and domain in the CRM username field. We then manually enter the additional user properties. Currently, I have my app creating the AD users but, being new to CRM, I am stumbling about figuring out how to utilize the sdk to add my users in CRM. Also, I wonder if there is a better way to go about this.
Any help or guidance would be greatly appreciated.
Try starting with this from the online MSDN reference:
Sample: Create an on-premises user
I have a simple ISV page (using 2007 service endpoints, 4.0 SDK) that only shows the Identity of a user who has opened it.
System.Security.Principal.WindowsIdentity.GetCurrent().Name
This page in CRM 4.0 shows a valid user DOMAIN\USERNAME
When this page is deployed to CRM 2011 it only shows NT AUTHORITY\NETWORK SERVICE
The CRM 2011 has a Claims Based authentication configured together with IFD. There is a STS server and Credentials. All connections seem work fine. The page is accessed via: https://servername.domain.com/organization/main.aspx and in an intranet environment.
It just looks that the page can not pickup the identity of a user who has opened it.
Have you experienced this before? Is there something not configured correctly?
Thank you for your help.
To be sure what user is logged on you can use WhoAmI message. In that way you are able retrieve full information about the user.
Also ASP.Net provide a way to retrieve currently logged in user HttpContext.User Property. But it could contains different values, depending on Authentication Type. In case of IFD with claims-based authentication, HttpContext.User will contains id of SystemUser entity.