All posts by ManuelGR

Microsoft Dynamics 365 Customer Engagement Consultant Speciality: Field Service

Business Rule not visible on custom Form

When you are creating an additional Form and have Business Rules with Scope “All Forms”

from another Managed Solution for that Entity, don’t wonder that the Business Rules do not appear on your custom Form.

Form opened in Unmanaged Solution after selecting a Field affected by the Business Rule

However you can find them when opening your custom Form not in your own Unmanaged Solution, but in the Default Solution.

Same Form opened in the Default Solution => Business Rule appears.

So don’t wonder, if Business Rules trigger for your custom Form, which you haven’t had in mind when only checking the Form editors Business rule area.

Learning: If you wanna know which Business Rules are using the arranged Fields on your custom Form, go to the Default Solution! Get a better overview of a Field’s involvement by opening your custom Form from there.

Share it on

Missing functionalities in new Solution Explorer / new Customization Experience pt. 1

Finally I started using the new customization experience on a regular base and in general I have to admit that I really like it. However there are still some shortcomings compared to our good old Solution Explorer.

More (white) space

One thing is that it takes more space in many aspects, because, at least this is what I think, Microsoft wants to be ready for touch screen users using and customizing) their system.

As this is related not only to the customization experience but also in general to the front end of all Model Driven Apps, I would really wish to have a button or setting somewhere the Personal Settings where I as a User can switch between mouse usage and touch usage. But at the moment I don’t think that this is somewhere in focus for MS.

On the other hand my assumption is that having a more streamlined customization portal that is more aligned to the front end saves valuable developer resources for MS because UI adjustments always take some additional time.

Missing Table Name (Primary Entity) in Processes View

In the old experience you could easily see which table/entity a Process is based on:

In our new experience this column is not there anymore which makes it unnecessarily hard to get an overview of which processes are used on which table.

Therefore I’m still preferring the old entry gate for customizing processes.

Missing Description column

In the old component overview we had a column “Description”. I often use this to leave a kind of technical hint like “Used on Contact-Form”.

In new component lists I’m really missing that column:

Missing Publish-button on “entity” level

In old experience we had this useful Publish button on entity level. You could press it to publish only components from the same entity/table at once. This happens often that after having edited something you just want to publish this table/entity only.

In the new experience I can’t really find something similar an entity level. Only after editing a View or a Form or similar you can publish this single component.
Publishing the whole solution however takes much longer than what it took to publish the Entity only.

Share it on

Visualize this view – Power BI Licence

If you are using this (currently preview) functionality in Dynamics 365 or Power Apps Model Driven App Views:

You might be confronted with this:

If so, don’t hesitate to click on “Sign up” here! The only this this currently does is, assigning you one of the unlimited power BI licenses.

You could even go the other way around and assign your users the upper mentioned license upfront to avoid for them getting this screen displayed at all.

Share it on

AI for Good

Microsoft unterstützt die Anwendung von Artificial Intelligence zu Zwecken des Allgemeinwohls. Die Landing Page hierfür ist

Nicht nur sollten AI-Entwickler schauen, dass ihre Datengrundlagen nicht einseitig sind, sie sollten ebenso darauf achten, dass sie nicht zu diskriminierenden Ergebnissen führen. Bspw. wenn man über eine Gesichtserkennung versuchen würde, die Kreditfähigkeit einer Person festzustellen, wäre das vermutlich ethisch nicht vertretbar.

Microsoft folgt sechs ethischen Prinzipien bei der Bereitstellung ihrer AI basierten Cognitive Services:

  • Fairness
  • Inclusiveness
  • Transparency
  • Save and reliable to use
  • Privacy protection of users
  • Accountable

Auch ein AI-Entwicklungsteam selbst sollte divers sein, um einer einseitigen Sammlung und Darstellung der Daten vorzubeugen.

Microsoft hilft bei der Demokratisierung von AI u.a. durch Power Apps und die Power Plattform:

oder mit dem Bereitstellen verschiedener AI-Services:

Neben dem Angebot vergünstigter Ressourcen für NGO’s veranstaltet Microsoft auch immer wieder Wettbewerbe, um neue “for Good” Ideen zu fördern.

Quelle und Inspiration:

Stefano Tempesta, Senior Program Manager at Microsoft in
AI for Good – 1st Episode of Global AI Podcast:

Weitere Informationen:
The Good Citizen Developers Playlist of Meetup Sessions given by Stefano Tempesta zu AI for Good:

Share it on

Mobile Offline Work Order Report

There is an OOB Work Order Report which can be generated even offline by the mobile application.

It contains the signature of the customer captured via the mobile device. The outcome is a PDF that can be attached to a Work Order.

It can also be sent out to a customer by email, however – of course – online is required for that mail.


To adjust the content an dformat of this Work Order Report (PDF Output) the sistem integrator has to adjust a PCF-Control using Visual Studio Code.

An alternative I think is still to use “kind of old school but proven” DocumentsCorePack (DCP) report (highly and easily customizable via MS Word) and let the report be generated when back online via the DCP-Server.

The big question, as this was a weakness in the former mobile signature process where the signature was stored as a picture file attachment within a Note, how does the new mobile app handle the storage of the signature…

It looks like it is stored as a base64 field directly on the Booking:

That means for tools like DCP (or Power Automate) that they have to “interpret” this file format if one wants to use these for a creating a report using the signature.

Share it on

New Schedule Board


The map is now available an the new Schedule Board:

Zoom in:

The route of a single Resource can be shown.
Route of all Resources can also be shown.
Sequence of Bookings of a Resource can be displayed. as well as a tooltip info about a Resource on the map.

The map can show:

  • Unscheduled Work Orders
  • Scheduled Bookings
  • Current Locations of your Field Ressources
  • Organizational Units
  • Routes
  • Traffic
Like in old Schedule Board you can drag a route onto a Requirement to create a Booking for a job that is on the way.

Improved daily weekly and monthly view

See the Microsoft detailed explanation video from this spot (for around 5 Minutes):

Available now in new Schedule Board

Improved for jobs covering multiple days or weeks in viewing and editing of Bookings.

Pop up:

Booking can be edited by right click => Edit
Every day of a multiday booking can be adjusted separately.



Share it on

Knowledge Articles for Field Service

  • was available for a long time for Customer Service / Cases
  • now available for Field Service, also offline
  • rich text including pictures, hyperlinks etc.
  • Pictures aren’t available offline [improve@microsoft]

Directly available in Field Service menu now:

  • can be associated to Cases, Work Orders, Customer Assets, Products & Incident Types
  • Knowledge Articles are taken over from a Case into the Work Order, if the Work Order is created out of that Case
  • also if Knowledge Articles are associated with a Customer Asset and/or Incident Types, Knowledge Articles are automatically available at the Work Order

And remember: if you have a Portal, your Knowledge Base is thought to be exposed to your customer base from there as well.



Share it on

Functional Location examined

  • to model out the location structure of a larger site
  • i.e. Building, Floor and Room on different levels
  • can also be used when not having a fixed location or location is frequently changing
  • Assets and Locations can easily be moved or reparented (drag n drop) if their location changes
  • Locations can be manually ordered by drag n drop
  • can be Physical or Functional location
  • available on mobile where technicians can add locations and assets
  • Address in Work Order gets updated according to the Functional Location Address, or if this is empty, the system searches across all Parents Location’s addresses (on more than one level!), and takes these if found
  • In Work Order form when first picking a Primary Incident Customer Asset, then the Functional Location gets auto-populated
  • After creating a Work Order, the Primary WO Incident will also be related to the Functional Location chosen in the WO
  • Creating a second WO Incident does NOT automatically relate the WO’s Functional Location to this 2nd WO Incident. Instead it can be manually set i.e. to another Functional Location (or create field mapping if you want it to be the same.)

Data Model of Functional Location

  • possibility to add individual address which automatically gets geo coded
  • 1:n Subgrids:
    • Customer Assets
    • Work Orders
    • Cases
    • Work Order Incidents
    • Agreement Booking Incidents
  • native N:N relationship to Account

So if a User would want to track Work Order Products, WO Services, WO Service Tasks on it, the Functional Location is NOT the best table to use. This brings us to the decision that a HVAC Unit and its components like Compressor, Fan, Thermostat… are better represented as Customer Asset than as Functional Locations (see screen above and note the different symbols for Location versus Asset).

Why N:N relationship to Account?

Imagine you have a big campus and you have different Service Accounts responsible for managing Work Orders of different typesbe .

Or a big construction site with different subcontractors working on the same Functional Locations and Assets.

=> This helps to be flexible enough to have those Locations used be more than one Service Account.

To keep in mind with hierarchies and lookup prefilters here

Functional Location lookup field on Work Order

When creating a Work Order the Functional Locations are prefiltered to those of the Service Account.

Note: Creating a new Asset from the hierarchical tree view f the Account form automatically adds the Account to the created Asset.
However creating a new Functional Location from the hierarchical tree view does ONLY automatically ad the Account to the created Location if that is on the highest level directly under the Account.

When adding a Functional Location to a Work Order after the Service Account has been filled in, only those Locations are suggested by the OOB Lookup View that have the Service Account directly related or related to one of the parent Locations (also over more than one hierarchy level).
However if you’re either removing the Parent Location on the Location form or if you remove the Service Account from the N:N subgrid of the highest level Location, then your Locations won’t be found by the Functional Location Lookup view on the Work Order or Case form anymore. You would need to click Change View and then guess which Location was the one you needed.

I personally think it would be more convenient if Microsoft would automatically add the Account to all levels of Functional Location when created from Account form, as it does for the Customer Asset [improve@microsoft]. A user could still delete the Account from the N:N subgrid if not needed.

Until than it could be solved by a custom cloud flow.

Primary Incident Customer Asset lookup field on Work Order

When creating a Work Order the Primary Incident Customer Asset lookup is prefiltered by the Functional Location chosen before, but only for the Assets that are directly related to the Functional Location via ‘Customer Asset’.’Functional Location’ lookup, not for the Child Assets of such an Asset. Why? The child assets do not automatically inherit the Functional Location of the Parent Asset.

With such a setup

With the hierarchy above you wouldn’t find any Asset when chosing Basement and you would still not find Monitor 1 when chosing Room 005. However you can click Change View and remove this flag and then be able to get a list of all Assets of the Service Account:

Depending on your use cases you could surely also solve this by a custom process (Workflow/Flow) that updates the Child Asset’s Location to the Parent Asset’s Location each time there’s a change in the Asset hierarchy.

Customer Asset Form

In a Microsoft Video there is a Customer Asset Form visible in a browser that contains the new Functional Location/Asset-Hierarchy-View:

I wasn’t able to find this form in my latest OOB installation until I found out that I need the Security Role Field Service – Resource to be able to see the form Customer Asset – Mobile (below screenshot). Being “just” System Admin is not enough to get this form provided ;-).

Tip: As stated somewhere else in relation to WO Products and WO Services already, if you’re customizing Field Service, make sure to also assign yourself the other Field Service Security Roles available OOB. System Admin role does NOT provide you access to all the forms used in Field Service [improve@microsoft].

Account form

Here it is to mention that only those Assets are visible in the new hierarchy control if one of the parent Functional Locations is related to the Account AND the Top-Level Asset (aka Master Asset) belongs to the Account.

This could also be a little bit improved [improve@microsoft] so that also Asset Hierarchies/Assets are visible that have no Functional Location related to the Account but where only one of the parent assets or at least the Asset itself is related to the Account.

So if you use this feature on the Account form make sure to always add your Functional Locations to all necessary Accounts (n:n) and remember that Assets only show up on the Account form if the Master Asset belongs to the account.

Also remember, that on the Asset Form you might get a better overview of how the Asset in embedded in the Location/Asset structure.

Self Scheduling Portal

In this new portal the Functional Location is displayed next to the affected Customer Asset for which you are Scheduling a Service Call/Technician:


Closing Words

Even if there are still some things to consider and improve, in general this is a very great addition to overall Field Service functionality as many Field Service organizations have a need for a deeper structuring of their locations. Servicing industry clients regularly needs more specific information for the field tech about where to go than simply the main Service Account address.

We even had a need to create graphical inhouse maps of floors and rooms to make transparent where exactly the work has to be done.

The much improved flexibility that comes with Functional Locations can be used for rental services or large machinery, which regularly change places (like construction machines, trains, ships, and similar).

Also I think the long standing problem of a Return & Repair process could be addressed with a Functional Location similar to a “Repair Warehouse”.

A great combination is the new ability to “Disable Customer Asset Validation” which turns off the necessity that a Customer Asset handled during a Work Order needs to belong to the Service Account of the Work Order.

More information:

18 Min. introduction Video by MS Field Service Team:

Our D365 Goddess Dian Taylor:

And of course Microsoft Docs (thanks to Dave Clark & Dan Gittler):

Share it on

Work Order Product and Work Order Service customizations

OOB Forms disappear

Attention! When customizing WO Product or WO Service form and do that how I sometimes do by creating own custom forms, you might stumble across the default forms not being visible anymore. That is because the default “Information” forms for both are only enabled for the following Security Roles:

  • Field Service – Administrator
  • Field Service – Dispatcher
  • Field Service – Inventory Purchase

What of course is strange and missing is the enablement for System Admin [improve@microsoft]!!

So what I recommend is as long as you’re customizing Field Service to assign your own User the Field Service – Administrator role additionally to System Admin.

Hide price and cost related fields

My “fastest” resolution has been to create a Hidden Tab and put all the unnecessary fields in it. This way you’re not getting in trouble when trying to remove fields that aren’t supposed to be removed from the form.

However I thing Microsoft is working on a general solution on how to disable pricing for Field Service in general because there have been so many customers not using pricing in Field Service but keeping it completely in their ERP.

Share it on

Appointment Sync from Outlook and Dynamics Appointments to Schedule Board

With Wave 1 2021 Microsoft has released a revised integration of Appointments into Resource Scheduling.

After setting ‘Scheduling Parameter’.’Include Appointments’ to Yes, you’ll see all Dataverse Appointments on your Schedule Board including their colored Appointments Status. And that in between your other Bookings coming from Work Orders or Custom Entities etc.:

Screenshot of the schedule board with appointments.
Source: Microsoft
  • Appointments that were tracked from Outlook
    “Dataverse appointments can also originate in Outlook, and be synced to Dynamics 365 if server-side synchronization has been set up. An Outlook appointment must be manually assigned the special Tracked to Dynamics 365 category so it appears as a Dataverse appointment record.”
  • Appointments from Service Calendar
  • CRM/Dataverse Appointments coming from Timeline or other Activity entries
    “Appointments will be visible on the new schedule board for the required attendees and the owner, as long as they are set up as bookable resources.”


  • Appointments can’t be moved in Schedule Board
  • can be deactivated for certain Resources in ‘Bookable Resource’.’Include Appointments’
  • RSO respects the Appointments
  • Schedule Assistant (Find availability) will also respect it (coming wave 2 2021)
  • “Appointments marked private in Outlook will not show their subject on the schedule board”

Source & more information:

Watch 7 min Video here:

Share it on

Links für Nonprofits, die Microsoft einführen wollen

Microsoft 365 Business kostenlos für Nonprofits.

Es gibt viele weitere sehr günstige oder kostenlose Software-Angebote von Microsoft für Nonprofits.



Hier kann man prüfen lassen, ob die eigene Organisation anspruchsberechtigt ist oder nicht:

Auf Deutsch:

Im Zweifel kann man über “Kontakt” auf der Seite direkt bei MS nachfragen.

Share it on

Power BI für Nonprofits

Power BI ist das laut Gartner absolut führende BI Tool, weit vor Konkurrenten wie Tableau oder Qlik. Siehe hier.

Mit Power BI kann man kostenlos starten, indem man sich Power BI Desktop installiert.

Wenn man einen interaktiven BI-Report teilen möchte, müssen Ersteller und Empfänger allerdings Power BI Pro haben.

Die Lizenz kostet für Nonprofits 3 USD pro Monat und User.

Weitere Infos:

Share it on

Customer Voice Surveys

Customer Voice ist ein Umfragetool.

Q: Dynamics Licencing Guide April 2021

Customer Voice wird per Tenant lizenziert (200 USD oder 168,70 €/Monat) plus Kapazität an Anzahl Antworten (Responses) zu den verteilten Surveys.

Kunden mit D365 Sales Enterprise, Customer Service Enterprise, Customer Insights, Field Service, Marketing, und Human Resources bekommen automatisch eine Customer Voice Lizenz und haben 2000 (Responses) im Monat frei.

Die gekaufte Anzahl Responses wird gepoolt über den Tenant, kann aber über Office Sicherheitsgruppen a.u. verschiedenen Umgebungen zugeteilt werden.

Zusätzliche Response Packages gibt es mit 1000 Responses pro Monat. Diese kosten 100 USD oder 84,30 €/Monat.
Nonprofit-Preis: 33,70 €/Monat oder weniger.


Mehr Infos zu Preisen:

Share it on