In some scenarios we all have to refresh or navigate to specific entity view after a particular action performed. We can use a method called navigateTo() for this requirement. This method is available under new Namespace Navigate.
This is a common issue everyone would have faced once in a while that the customizations were not getting applied on the target instance through solution deployment. This is due to the direct changes on the component which is part of managed solution.
A component which is managed, gets an unmanaged layer as soon as you edit it directly on the instance. This unmanaged (active) layer lays on top of all other layers, which are coming from the different solutions containing this component. The layer on top is always winning, hence you can’t see the new changes coming from new deployments.
To avoid this issue, Microsoft introduced a new feature called “Solution Layers” where you can see all solutions where this component is part of it. You can see one “Active” solution on top of all solutions if you would have changed something directly on the instance. So, to get rid of the unmanaged customizations on managed component, you have to follow the below steps.
Select the component and Click on “Solution Layers” button (some times you can see this option under “More Actions” drop down menu).
2. On click of this button, it will show the list of all solutions which included selected component, as shown in the below screenshot.
3. Select the 3 dots (…) of “Active” solution row, select “Remove Active Custmoziations” option and confirm.
4. That’s all you have to do to remove all unmanaged customizations, after that the changes will be affected which are coming from new deployments.
I faced this situation so many times, the changes I have done for ex. in web resources in dev instance couldn’t transfer to UAT/Prod instance due to the “Active” solution layer. So with this new feature, you could remove this unwanted solution layer with a single button click.
Note: Microsoft not yet rolled out this feature for some components like Views and Fields. (Thanks Viswanath for highlighting this in your comment)
I am very happy to announce that my first plugin “Business Unit Hierarchy” is listed in XrmToolBox now.
Thanks to Nishant Rana for giving me an idea to develop this.
This plugin is simple but very useful. Most of the times we navigate to so many windows to understand the BU hierarchy in our organization (I faced this situation many times) but with this plugin it is very easy to get the complete overview of BU Hierarchy. I plotted the BU Hierarchy in tree view presentation which is easy to understand for any user.
Here are list of steps to use this plugin
Install “Business Unit Hierarchy” plugin from XrmToolBox Plugins Store.
Connect to your organization.
Open the plugin and click on “Load Business Unit Hierarchy” button.
That’s it, Business Units of your organization will be loaded in a hierarchical structure like in the above screenshot. The BU’s that are loaded in red color are disabled ones. Select any BU to see all the Users and Teams under this.
Hope it helps to everyone and saves time to understand the BU Hierarchy.
Today while exploring new stuff, I found very interesting tool for developers which is called XRM.Tools. I would like to share this with all of you. It provides a set of tools which gives you overall picture on particular things like Security Roles, Business Rules, Server Trigger and etc. The main advantage with this tool is, no need to download or install unlike XRM ToolBox (everything in cloud)
Available Tools under XRM.Tools
Business Rule Explorer
Security Role Explorer
Server Trigger Explorer
Access Token Generator
Web API Builder
Auto Number Creator
Azure Region Check
I would recommend everyone to go through this link where David Yack explained everything about how to use this tool.
Note: As a developer, you have a chance to build and contribute a new tool.
Recently I worked on one project where I integrated the contacts and groups from SharePoint to Exchange Online. I want to share the approach that I followed to do this.
I used PowerShell scripts to create objects (Contacts and Groups) in Exchange Online. Initially, I thought of using Azure Functions with C#, but it’s not possible as there is no API exposed for Exchange Online. I used MS Flow to trigger my PowerShell scripts that I have developed in Runbooks (Azure Automation) on Create/Update of sharepoint list item. We have an action in Flow to create a job of a particular Runbook (Azure Automation –> Create job).
The reason to use MS Flow for this requirement is to develop an application with low-code which facilitates the customer to perform some basic changes without need of a developer.
While working on one PowerApp, I observed that the code written in first screen “OnVisible” event is not executing which means OnVisible event is not firing. I found couple of workarounds for this issue.
Workaround 1: Add a welcome screen with a simple button which will navigate to your actual screen.
Workaround 2: If you don’t like the Idea of having a welcome screen, you can use this one. Place a timer control on the screen (make it invisible and sent to back) and write the code in “OnTimerEnd” event.