Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
How can redirect an external user after he login on the n Dynamics 365 web page .
I want to redirect the user to another web page to create manually a user and assign the right to create ticket.
What is the best way to proceed ?
Let me clarify what I mean.
I created an external user and the external user is able to logon on the Dynamics 365 Portal.
But after he logon I want to redirec the external user to the Portal admin Webpage to select a contact and assign or remove a web role to an existing contact
And also to Entity Permission.
On the first image the external user already logging .
I want to know how to redirect to second page.
I joined 2 images.
Looks like you're wanting your Portal users to access Dynamics 365 directly? That's not typically how it works (unless you want to have D365 licenses for all of your Portal users).
You can achieve the functionality you're looking for, but it should be built in the Portal, not by redirecting them to the Dynamics interface. I'd recommend having a look at the Partner Portal template, which has example of how you can allow Portal users to invite other people, and to change their roles. In that case, there is a field on the contact record where you set which level of permissions they should have. Behind the scenes in Dynamics there are workflows that trigger when that field changes and updates the contact's web roles.
Hope that makes sense.
Good evening M.Hayduk, I ‘m using the customer self service portal .
How can apply that for customer self service portal ?
What is the best approach ?
How can add in interface to add or remove authorized user .
Those use will be authorize to create ticket ?
Using Entity Lists and Entity Forms, you can allow users to create/manage contacts.
When a new user is created using the Entity Form, you can use a workflow/flow to invite them to the portal (so they can setup a username/password).
Setup the various Web Roles for the permissions you want. You can add a field to the contact record that defines which permissions they should have. Then create a workflow/flow that fires when that value changes that updates the contact's Web Role(s).
If you want to see the details, I'd recommend spinning up a trial instance and installing the Partner Portal. There you can see exactly how Microsoft accomplished it.
Good morning Expert !
What is the meaning of this error : field is present multiple times on this form. Only first field will be rendered in the UI ?
How can I find where is the error ?
What tool can I use ?
Thank you !
This means that the same field appears multiple times on the form. While this is supported in the regular Dynamics UI, it is not supported on the Portal.
So look for a field that appears twice (or more) on the form, and remove until there is only one instance.
Hope that helps.
Good evening ,
Do you understand this error message ?
An unknown failure has occurred. Error ID # [9f1229b1-db2a-4201-9ec9-d3853c484f46]
How can I find out the cause and resolve the issue ?
I'd recommend creating new threads for each issue, instead of reusing unrelated threads. It makes it easier for people that have the same issue as you in the future.
For the issues you're having, take a look at this blog post:
Business Applications communities