{Did you know} My Blog is Top 6th according to the feedspot

Hello Everyone,

Today i am going to share happy moments of my blog.

I have started this blog back in 2015 and when i look back, my blog have grown tremendously that i didn't imagined.

 Many thanks for viewers for encouraging me to do more blogs by visiting my blog and i have heard from my blog subscribers that my blog is helping them in there day to day jobs. It means alot for me. 

Today total views: 

60 Best Microsoft Dynamics 365/CRM Blogs & Websites:

Today my blog is top 6th blog in the world according to the www.feedspot.com under top 60 blogs Dynamics 365 Blogs category.

Click here

Have active 1000 followers on the feedspot.

100 Best CRM Blogs and Websites: 

Also top 50th blog in CRM Blogs according to the www.feedspot.com under the top 100 CRM Blogs category

Click here

Many thanks for Feedspot for chosing awarding my blog as their preferred blogs list.

I hope this helps

Malla Reddy(@UK365GUY)

{How to} make a copy of Dynamics 365 Field Service Model Driven App

Hello Everyone,

Today i am going to show how to create a model driven app from existing Dynamics 365 Field Service Model Driven App.

Lets gets started.

Suppose you have a requirement to create a Model Driven App  from existing MDA field service, need to add a custom entity into the sitemap, which should be included in the solution.

Login into www.admin.powerplatform.microsoft.com

Select the environment and open it.

Then go to settings and click on solutions and create a new solution:

Click on Model Driven App, a new pop window will be displayed, 

Fill in the Name, Unique Name and Optional descripition, select the CHECK box to use default image

and also CHECK box of Use existing solution to create the App.

Optional Welcome page check box, also Enable Mobile Offline and click on NEXT button.

A new window will pop up and select the "FIELD SERVICE " Solution and also select the site from the drop down, you can configure site map later if you want to, then you need to check the box on the screen to do that later.

Then click on done.

A new Model Driven App will be created as seen from the screen shot. 

Now i want to add my required entity to the site map and publish the map.

Check the newly created solution whether Model Driven App and XML solutions related to Field Service App created.

You can see the files added to the solution see from above screenshot.

Then publish the solution the changes.

Then check the new model driven app has been created on the App's area.

Thats all for today.

I hope this helps.

Malla Reddy(@UK365GUY)

{New} Scheduled Board view for Dynamics 365 Field Service

Hello Everyone,

Today i am going to share new scheduled board view on Dynamics 365 Field Service.

Lets gets started.

The first "+" to expand all resources bookings in the timeline.Similarly "-" symbol is to collapse the resource bookings.

Filters: 

You can filter by Characteristics - Rating, Roles of the resource, resource by territories, Organisation units, Resource types, Teams, Business Units to schedule bookings.

View:

You can view the board hourly, daily, weekly, monthly.

List view or Gants view:

List view will show the resources list.

Where as Gants view:

Gant view shows the all resources and scheduled work orders on the board.

Calendar:

With the Calender view you can adjust the dates with it.

Booking manually on the scheduled board using the Book icon:

Detail Panel:

Detail Panel will work when you "resource" and click on detail panel, it will details related to the resource.

Legend: 

Legend shows the booking status in color format, you can change these color from board settings too.

Booking status: Cancelled,  Commited, Completed, Hard, In Progress, On Break, Proposed, Scheduled, Soft, Travelling, Timelinen- Non Working Hours.

Booking Alert :

If there are any alerts related to bookings will be displayed here.

Map: 

Map view will show the bookings and there distance, requirements, Routes, Organisatio Units, Traffic, Grayscale.

 

Board View Settings:

Board View Settings allows all time zone , time resolution, row height, show cancelled, apply territory filter, show booked percentage and all board settings.

When you click on all board settings: 

Initial Public View will pop up, you can always change these settings according to your organisation requirements.

For example: When you expand Map, you can adjust the resource tooltips view to any view that is available like "active bookable resources(Default) or contact resources etc..

Simiraly you can make changes for scheduled assistant, Custom web resource where you can make custom customisation on the board.

Schedule Assistant: 

Schedule assistant allows to make changes to the view on the scheduled board for search for, unavailable resources, Available color, Partially available color, Book based on, default available icon, default unavailable icon, default partially available icon.

Simiraly for rest like "Board color" as discussed previously, other, schedule types like work orders, appointment, project, none, 

Requirement panel: 

with the requirement panels, you can change the panel view by clicking the "+" icon and also apply filters too.

You can refresh the board by clicking the refresh icon show below, also you can expand the full browser view by clicking littel arrow icon.

Finally on the scheduled footer area you can see the

 Open requirements, Project and Unscheduled Work Orders.

The allow view change on the scheduled board is MAP view which will be on the right hand side of the Scheduled board and some look and feel icons and settings too.

I hope this arcticle have shown some quick glimpse of the Dynamics 365 Field Service Schedule Board.

Malla Reddy(@UK365GUY)

{Do you know } Unable to create custom field on System Entity {Site} on Dynamics 365 Sales

Hello Everyone,

Today i am going to share my experience with the error message:

"The referencing entity of a relationship must have the CanBeRelatedEntityInRelationship managed property set to true"

So there is  a requirement to create a relationship between "SITE" AND "COUNTRY" TABLE in Dynamics 365 Sales Model Driven App.

When i went ahead and try to create a custom lookup field "country" on "SITE" table 

Error: "The referencing entity of a relationship must have the CanBeRelatedEntityInRelationship managed property set to true"

Unable to create custom field on site table because of restriction imposed by Microsoft by design.

Here is the fully customizable tables and customizable entities properties: Here 

So the Site Table has restriction on "CanBeRelatedEntityInRelationship" managed property to False.

 So in my case i am trying to create N-1 relationship between SITE and COUNTRY, which is not possible for my requirement. 

I thought i can use Site as a location and create relationship between country and site(location) which is not possible. so i will create a custom table for location and then create a relationship.

EntityMetadata properties that control customizations: refer to below screenshot:

Hope this helps

Malla Reddy(@UK365GUY)

{Do you know} Community tools for Microsoft Dynamics 365 & Power Platform - Dataverse

Hello Everyone,

Today i am going to share some of the useful tools for Microsoft Dataverse from Community is XRMTOOLBOX.

XRMTOOLBOX is a place for all community tools click here

It is a windows application connects to Dataverse, providing tools to ease customization and operational tasks.

Xrmtoolbox helps to customize or configure task easier and less time consuming.

Browser Extensions:

Level up for Dynamics 365/Power Apps:

The level up tool, helps us to quickly perform advanced/hidden actions in Dynamics 365/Power Apps, without bookmarklets.

Visual Studio Code Extensions:

Building own's extension for visual studio code the community has taken the benefits of this and has built several of them.

1. Dataverse Devtools : Helps to connect to a Dataverse environment general Typescript definitions for entities, create different type of Dataverse-specific projects and much more.

2. Power Apps Portal Helper : Set of commands that simplify working wirh Power Apps CLI for Portals.

3. PCF Builder : Helps with Initializing, building and testing Power Apps Components Framework components

I hope this helps

Malla Reddy(@UK365GUY)

{How to} Tools and Apps used in Application Lifecycle Management(ALM)

Hello Everyone,

Today i am going to show the tools and apps used in Application Life Cycle Management.

Lets gets started.

1. Power Platform Admin Center

PPAC provides administrators to manage environments and settings for power apps, power automate and model driven apps in Dynamics 365 Customer Engagement Apps.

Also manages data integration, gateways, data policies, and get key Microsoft Power Platform metrics through Microsoft Dataverse analytics, power automate analytics, power apps analytics.

2. Power Apps:

Power Apps is collection of apps and services, connectors and data platform that provides a rapid application development environment to build custom apps for any business needs.

It can be connected to business data stored in Microsoft 365, SQL Server etc.

3. Configuration Migration Tool: This tools enables to move configuration and or reference data between the environments. 

Note: Configuration/Reference data is different from user and transcational data and is used to define custom functionality in apps based on Dataverse.

Know more about the tool here

4. PowerShell Moduels: 

PowerShell cmdlets for administrators, app makers, and developers can automate many of the management and monitoring, quality assurance tasks that are only possible manually today in Power apps, the power platform admin center.

Click here

5. Pipelines:

Using Power Platform Pipeline admin create and configure pipelines so that makers can deploy the solution by click of a button into other environments like UAT or Production from Development.

 Tools and apps used by developers

1. DevOps: 

Power Apps build tools to automate common build and deployment tasks related to Power Apps if your DevOps platform is Azure DevOps.

DevOps is the combination of Software development and IT Operations. 

The primary goal of DevOps is the software development lifecycle and provide continuous integration continuous delivery(CI/CD) with quality software.

Microsoft Power Platform  Build Tools for Azure DevOps here

 

2. Version Control System: 

To keep track of the changes on the files  by keeping track of changes committed to softwate code.

 Getting started with GIT Here

3. Package Deployer:

    Lets administrators or developers deploy packages of relevant assets to Dataverse instances. Packages can consist of not only solution files but also flat files, custom code and HTML files. CDS  provides Visual studio template for creating packages that can be used with the package deployer tool or with PowerShell to deploy them to CDS Instance.

Learn more about Package Deployer Here

4.Solution Packager: 

It is a tool that can unpack a compressed solution file into multiple XML files and other files, so they can be easily managed by a source control system.

Learn more about Solution Packager Here

5. Power Platform CLI:

Its a single stop developer command line interface that empowers developers and app makers to create code components.

More about Power Platform CLI Here

 I hope this helps

Malla Reddy(@UK365GUY)

{How to} Key areas of Application Lifecycle management within Power Platform

Hello Everyone,

Today i am doing to touch on key areas of the Application lifecycle management.

So lets gets started.

Application lifecycle management which includes governance, development, maintenance.

Which also includes:

• disciplines
• maintenances
• change management
• support
• continous integration
• project management
• deployment
• release management
• governance 

It also provide communication and collaboration between software development teams and related departments, like test and operations.

Important areas of Application lifecycle management:

1. Governance: requirements management, resource management, nuturing and system administration such as data security, user access, change tracking, review, audit, deployment and rollback.
2. Application development: software development lifecycle, planning, design, building and testing the application and continuous improvement.
3. Maintenance: Deployment of app and maintenance of dependent technologies.

As you can see from below image: Application lifecycle is circular development process.

Areas: Plan & track, develop, build and test, deploy, operate, monitor & learn from discovery.

ALM is for Power Apps, Power Automate, Power Virtual Agents and Dataverse.

Microsoft Dataverse lets securely store and manage data and processes that's used by business applications.

To use Power Platform features and tools available to manage ALM, all environments that participate in ALM must include a Dataverse database.

Solutions are the mechanism for implementing ALM.  Solutions are used to export and import across environments.

Dataverse stores all artifacts including solutions.

Source control is for storing and collaborating on your components.

CI/CD Continuous integration and  continuous delivery like Azure DevOps, which allows to automate, build test and deployment pipeline.

I hope this helps

Malla Reddy(@UK365GUY)