So let’s get started!

If you’re an administrator in Power Platform Admin Center, you might have heard of Maker Welcome Content. It’s a feature that allows you to create custom welcome screens for your app makers.

Maker Welcome Content is a feature in Power Platform Admin Center that allows administrators to create custom welcome screens for their app makers when they get started with Power Apps.

It’s a great way to provide a personalized experience to your users and make them feel welcomed. Maker Welcome Content can include text, images, and videos to help app makers understand the purpose and use of the environment.

Maker Welcome Content is displayed to app makers when they sign in to the environment. It’s a one-time experience, and they won’t see the welcome screen again unless you make changes to it.  In case you have enabled it, users will be able to see customized welcome content every time they sign in to the Power Apps portal. You can add help content, it will replace the default Power Apps first-time experience page content. Moreover, you can customize Maker Welcome Content for different environments, so each environment can have its own welcome screen.

The below steps will help you enable Maker Welcome Content:

1. Sign in to the Power Platform admin center.

2. Click on the Environments option from the left panel > Select the specific managed environment from the list > Click on Edit Managed Environment as shown in the screenshot below:

3. After clicking on the Edit Managed Environments option, it opens the editor window of the environment which contains the Maker welcome content option. You can create the welcome page > Enter Welcome or Help content in the text box under Maker Welcome content as shown in the screenshot below. You can enter simple text or Markdown for your content.

4. If you want to provide some blog or website links then you can enter a link into Learn More URL box.

5. After configuring the welcome content click on Preview in the new tab option to quickly preview your welcome page.

Please follow the below step to see your Welcome Content Page in Power Apps:

Step 1: Login Power Apps portal and select a specific environment from the list > Welcome page will show as follow when the user login into Power Apps. Users can select the ‘Don’t show this again here’ option if the user doesn’t want to see welcome content again.

Step 2: There is one more option to see your welcome page after selecting the environment. Select Learn option from the left navigation > Click on From your org tab it will show your custom welcome content page as shown in the screenshot below.

Conclusion

‘Maker Welcome Content’ is a powerful feature that can help organizations improve end-user adoption of the Power Platform. By providing users with custom welcome messages, organizations can ensure that their end-users have the resources they need to get started with the Power Platform. As organizations continue to explore the capabilities of the Power Platform, ‘Maker Welcome Content’ will play an increasingly important role in driving adoption and success.

The post ‘Maker Welcome Content’ Option in Power Platform Admin Center first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post ‘Maker Welcome Content’ Option in Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.

In this blog, we will explore, how we apply Solution Checker in managed environments. Solution checkers can be used to enforce thorough static analysis checks on your solutions against a set of best practice guidelines and spot problematic patterns in managed environments. When importing solutions into a managed environment, Solution Checker verifies security and reliability at each stage.

Please follow the below steps to enable Solution Checker on your environment:

1. Sign in to the Power Platform admin center.

2. Click on Environments from the left navigation panel > Select the specific environment from the list > Select Enable Managed Environments as shown in the screenshot below

3. After selecting the Enable Managed Environments option, the environment’s editor window appears and displays the solution checker option, which assists you in selecting the appropriate setting under Solution Checker as in the screenshot below

We can apply the Solution Checker process in three different ways as follows:

1. None

Using this we can skip the entire Solution Checker process. If we select the None option, it will disable the automatic solution validations process while importing any solution.

2. Warn

Whenever you import a solution, all custom solutions will be automatically checked. You will get a notification when a solution is detected with highly critical issues, but the importing process will be executed. If everything is good to import, then the solution will be successfully imported. After a successful import, an alert is popped up if the imported solution has validation problems. There is also a hyperlink along the message named ‘Download log’. When you click on it then an XML file will be downloaded which contains the details of issues that occurred while importing the solution.

3. Block

Whenever you import a solution, all custom solutions are automatically checked. When a solution is detected with serious problems, the import operation will be stopped and a notification regarding validation problems will be displayed. Considering this occurs before the import process, the environment will not have any impact, due to import failure.

There is also a hyperlink along the message named ‘Download log’. When you click on it an XML file will be downloaded which contains the details of issues that occurred while importing the solution.

Send email messages to the admin

In Solution Checker, the admin could have received the mail reading result of solution validation done by the solution checker. To this, you have to check send email checkbox as shown in the screenshot below:

Conclusion

Using Solution Checker, we can validate custom solutions during their import process and also get suggestions to resolve the errors.

The post How to validate solution using Solution Checker in the Power Platform Admin Center first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post How to validate solution using Solution Checker in the Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.

In our previous blog, we have already explained the enhancements available while setting up the security model in Microsoft Dataverse. While exploring, then, the UI setting was not available for displaying security roles across business units.

There is a setting available named “Record ownership across business units (Preview)” in the Power Platform Admin Center which is in PREVIEW for a long time.

Need:

With this new feature, you can add security roles from other business units to a user besides the user’s standard business unit. The result is that users have privileges from their security roles in their business unit as well as privileges from the other security roles from the other business units.

Configuration:

Sign in to the  Power Platform Admin Center select the Environments tab, and then choose the environment that you want to enable this feature.

Select Settings > Product > Features > Record ownership across business units (Preview) > Turn on the toggle as shown:

NOTE:

• By default this feature is disabled and needs to turn on manually.

This feature changes the way we were managing the security roles till now. If you are thinking to implement the “Role-based security model” then if you remember the security roles were created at the root level and these security roles were inherited by the child business units.

But with this feature, you are now allowed to create a security role at individual BU as well. You can either create a new role from scratch or copy the existing role in the child BU itself, independent of the parent BU.

Use Case:

Let’s say you have two different business units (BU1, and BU2) with different groups of users.

Let’s say “Paulina” belongs to “BU1” and has BU level access as shown below, If she needs access to data created in “BU2” then below are the possibilities:

NOTE:

• BU1 and BU2 are child BU’s of another BU “Innosight” and they are independent of each other.
• If BU1 and BU2 were child BUs of each other then providing parent-child BU access level would have provided the access across the BUs (through Business units hierarchy).

There are a lot of possibilities around to achieve this in Dynamics 365. For example, record sharing, hierarchy security, business unit hierarchy, and team ownership.

Out of all these possibilities, the new modernized business unit structure brings a more enhanced and easy way of doing it.

Before turning on this functionality, if you observe the manage security role page then you will experience that changing/selecting another BU is not allowed.

Navigate to Environments > Select an appropriate environment  > Settings > Users > Select the user > Manage Security roles. On this page you can observe changing the BU is not allowed:

After turning on this functionality you have the flexibility to change the BU and can assign the desired security role from the respective BU among the list.

As shown below created the “BU2 Salesperson” role under “BU2” and assigned this to “Paulina”

“Paulina” can now access records from both BU1 and BU2 even though “Paulina” belong to BU1. This is because we have assigned security roles to the “Paulina” from BU2 as well.

Though “Paulina” belongs to BU1, roles from other BU (i.e. BU2) can be assigned, Refer to the below screenshot:

As “Paulina” user have a security role from BU1 and BU2 which allows her to access both BUs data as shown:

Conclusion

By using this feature users can easily assign the security roles independent of BUs and can access the data from other BUs with little effort

Ps: Our favorite Community Summit is back trending with #MySummitNA – Eagerly awaiting to meet our CRM friends in person. Inogic will be at Booth #1334 at the Summit, Gaylord Palms, Orlando, FL from 10^th to 13^th October 2022. Do block your calendars for 12.15 pm on Oct 12^th for our Partner Solution Showcase session Maps for CRM – Maplytics by our CEO at Room Coastal 7 – Convention Center, Level 2. Register now using our Promo Code INOGIC10, and avail of 10% off on your registration! 

Please visit the Source and support them

The post Record ownership across business units (PREVIEW) appeared first on Microsoft Dynamics 365 Blog.

In this blog, we will see how to enable Administration Mode from Power Platform Admin Center. Enabling the Administration Mode comes in handy while performing operational changes to the environment like copying a sandbox instance to the production. Previously, this setting was available from the Office 365 portal for sandbox instances. For more details, you can refer to this blog.

Administration Mode can be enabled for Sandbox, Production, and Trial (Subscription-based) instances. So once enabled, only the users with the security role of System Administrator and System Customizer can access the environment. Enabling the Administration Mode ensures that neither non-administrators nor administrators affect each other’s work.

Let’s see how to configure ‘Administration Mode’:

1. Navigate to Power Platform Admin Center Login with Environment Admin or System Administrator -> Navigate to Environment from the left-side menu.

2. Select the Environment and Click on Open.

3. In Details, select Edit.

4. Enable the Administration Mode.

5. Post enabling the Administration mode, you will get the option to disable or enable the Background Operation. By default, this option is enabled.

If you disable the Background Operation, it will disable all asynchronous operations like workflow, and synchronization with Exchange.

6. Now the Custom Message field is no more editable as it is being removed -> Click on Save.
7. After saving, the environment gets updated.

Once it is completed, you can see a notification on the Environment page stating that ‘This environment is currently in administration mode, so only admins can sign in to it. You can turn off administration mode in settings’.

Now, only users with System Administrator or System Customizer security role can successfully access the environment.

Whereas, other end users i.e. non-admin users will not be able to access the environment.

Conclusion:

In this way, administrators can manage and maintain the environment by setting it in the ‘Administration Mode’ from Power Platform Admin Center.

Please visit the Source and support them

The post Enable Administration Mode from Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.