Skip to main content

Posts

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
Recent posts

SharePoint User Group Bulgaria

In the past year I invested my free time in activities related to the SharePoint User Group Bulgaria. This is the reason why I stopped writing in this blog. Please start following this new place  www.sugbg.com . I promise you that you will find there truly valuable content.

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage. In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API. The scenario I'm going to use is simple - migrate single Document library with single document. The document has one taxonomy column (MyTaxonomy) and three versions: Here are the steps: Step 1: Export the document library Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4 This command will export the document library and will create the initial package. The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the

The task is 102.69% completed.

I did several tests playing with the Zero Downtime Patching feature and found that the developers in Microsoft have overfulfilled this task. Or they just have dirty subconsciousness and have added  69  in the status bar ... Being serious I must honestly say - this feature is extremely helpful. Test it! And the above screenshot is not manipulated. I saw it several times while upgrading the servers.

SharePoint 2016: High Availability Farm Topology

MinRole concept was introduced in SharePoint 2016 and it aims to simplify the process of designing the farms. However, I still find ambiguous information about the count of servers in SharePoint 2016 farm. Let's ask ourselves the question - What is the minimum number of servers which allow High Availability MinRole farm? According to technet   we have the following options: Small High Availability (HA) MinRole farm 4 Four servers with two shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application with Search servers Medium High Availability (HA) MinRole farm (Search optimized) 6 Six servers with both dedicated and shared roles: ·         Two Front-end with Distributed Cache servers ·         Two Application servers ·         Two Search servers Medium High Availability (HA) MinRole farm (user optimized) 6 Six servers with both dedicated and shared roles

Show\Hide columns in the SharePoint default list forms

Here are two cases that I face in the daily work with SharePoint which I find very common and would like to provide some technical details. 1. Hide Yes\No column If you want ho hide an Yes\No column inside content type, surprisingly you find that you can't. Or to be more specific, the SharePoint interface won't allow you to do it. I'm not sure why is that limitation but тхис is technically supported by SharePoint. Here is a JavaScript that modifies the column visibility. You just need to run it with user who have appropriate rights. var context = SP.ClientContext.get_current(); var siteContentTypes = context.get_web().get_contentTypes(); // add the GUID of you ContentType var myContentType = siteContentTypes.getById("0x010100185E5E735545B942852F513AEB77B51C"); var fieldLinks = myContentType.get_fieldLinks(); context.load(myContentType); context.load(fieldLinks); context.executeQueryAsync( function (sender, args) { var listEnumerator = fie

Load dynamically JavaScript file inside Custom Action

This starts to be very common scenario in the SharePoint online projects: You want to have custom actions (“My Action”) that execute custom logic. The main challenge is how to load the JavaScript file with this custom logic (/sites/demo/SiteAssets/Actions/dts.demo.script.js) only when the custom action needs it. One approach described in many posts is to use a Script link.  Here is a working example: function RegisterScriptLink() { var scriptBlock = 'var headID = document.getElementsByTagName("head")[0];var newScript = document.createElement("script");newScript.type = "text/javascript";newScript.src = "' scriptBlock += '/sites/demos/SiteAssets/Actions/dts.demo.script.js' + '?ver=' + ((new Date()) * 1); scriptBlock += '";headID.appendChild(newScript);'; var context = new SP.ClientContext.get_current; this.site = context.get_web(); var collU