Application User form is missing in Dynamics 365

The option to use Server-to-Server authentication in Dynamics 365 is an important technical approach. It consists of two elements:
1. Azure AD application
2. Dynamics 365 Application user created with the Azure AD application's ID
There are many posts about this concept, please do a search and learn it.

What I want to show you here is how to solve the problem - Application User form is missing:

In order to create an Application user through the web interface, you need to go to:
Settings -> Security -> Users -> New:

If everything is OK you will see the User's new form and the "Application User" option will be available:

If you don't see it, this mean that the form is not Active and you need to active it.

Here are the steps:

Step 1: Navigate to the Customise the System:

Step 2: Select User entity and choose Forms:

Step 3: Select the filter "All Forms"

Step 4: Select "Application User" form and click "Activate":

Step 5: Confirm the action:

Step 6: Publish the entity changes:

Now you should be able to see the Application User form option. (Don't forget to refresh the page with Ctrl + F5.

Comments

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed. The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before. There is a new control called ClientPeoplePicker . How to use it: 1. Add this references <% @ Register TagPrefix ="wssawc" Namespace ="Microsoft.SharePoint.WebControls" Assembly ="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 2. Add the following control declaration < wssawc : ClientPeoplePicker Required ="true" ValidationEnabled ="true" ID ="peoplePicker" runat ="server" InitialHelpText =" <% $Resources:wss,aclinv_PickerIntialHelperText %> " VisibleSu

Error: A duplicate field name "xxxx" was found

Soon I have some experience with migrating solution from SharePoint 2010 to SharePoint 2013. The migration was on 3 steps. First one was just to copy the custom fields, content types and list definitions from the old VS 2010 project into a new VS 2012 project for SharePoint 2013. Looks like pretty simple task but ….. The problem: Error “ A duplicate field name "xxxx" was found ” when the feature for provisioning the fields and content types is activated. The solution: Review the field definitions and make sure no field has Name property equal to some of the ‘reserved’ values. Explanations: In SharePoint 2010 there was no problem to have these fields as a definition of custom fields: < Field Type = " Note " ID = " {893FB9BC-2DA4-4451-A1D1-88010CDC6A08} " Name = " Description " StaticName = " Description " DisplayName = " Description 1 " Required = " FALSE " MaxL

Using SharePoint Attachments' controls with elevated security

The scenario: Create custom forms for Add/Edit/Delete items to a list which is not accessible by the regular users. The forms should support working with attachments. The problem: The default SharePoint controls don’t work if the current user doesn’t have access to the list items. The solution: Use custom code for generating the SharePoint default HTML so the out-of-the-box javascript works correct. Explanations: The scenario occurs when some list need to be hidden form the users. The list has broken security inheritance and users can't navigate directly to it. Working with its fields requires crating web warts or application pages with appropriate controls on them and server-side code running under elevated privileges. The issue here is that the OOTB (out-of-the-box) controls for Attachments don't work if the user doesn’t have access to the related list item. The OOTB controls are: AttachmentsField , AttachmentUpload , AttachmentButton . There is a lot of code

SPObject.Resolve()

Search This Blog