Microsoft Dynamics 365 and Power Platform Rss Feed

Using Azure Service Bus Queue to simplify Dataverse Concurrency

Have you ever faced a challenge where you needed to process bulk data that would update a single record? For example, you processed receipts for a single customer, and the program failed to update the correct data because the processing happened at almost the same time (concurrency issues). To simplify this process, we will learn … Continue reading "Using Azure Service Bus Queue to simplify Dataverse Concurrency"

https://temmyraharjo.wordpress.com/2025/06/23/using-azure-service-bus-queue-to-simplify-dataverse-concurrency/

Published on: 9 minutes ago

Outlook’s New Summarize Option for Email Attachments

Among the blizzard of Copilot changes is one where Outlook can summarize attachments. That sounds small, but the feature is pretty useful if you receive lots of messages with “classic” (file) attachments. Being able to see a quick summary of long documents is a real time saver, and it’s an example of a small change that helps users exploit AI. Naturally, it doesn’t work with Outlook classic.

https://office365itpros.com/2025/06/23/summarize-attachment-outlook/?utm_source=rss&utm_medium=rss&utm_campaign=summarize-attachment-outlook

Published on: 2 hours ago

SQL LIKE Operator & Wildcards | Pattern Matching in SQL Made Easy | SQL For Beginners | Ep 13

https://www.youtube.com/watch?v=MH7w8nH1SXw

Published on: 3 hours ago

[Resolved] Quick Find View is not Working or Loading in Dataverse Model Driven APP

When you work with Dataverse Data Modelling for tables, you sometimes edit Quick Find View but you will not see the Quick Find View when you search. Follow the below steps to resolve. Step -1 : Enable Setting navigate to Power Platform Admin Center of the selected environment and select the environment then go to…
Read more

https://softchief.com/2025/06/23/resolved-quick-find-view-is-not-working-or-loading-in-dataverse-model-driven-app/

Published on: 4 hours ago

Dynamics 365 Field Service : Configure the integrated map feature

In the world of field operations, location intelligence is key. The integrated map feature in Dynamics 365 Field Service enables dispatchers, service managers, and field technicians to visualize work orders, resources, and routes on a map. This not only enhances scheduling efficiency but also improves on-time delivery, reduces travel costs, and boosts customer satisfaction.

This blog will walk you through:

• Why the map feature matters
• The components involved
• How to configure it step-by-step
• Key settings to optimize
• Common use cases

Why Use the Integrated Map?

Field service operations are geographically distributed. By enabling the map feature, your organization can:

• Visualize work orders and resources
• Optimize technician routes
• Detect and solve geographical bottlenecks
• Perform geo-fencing and proximity-based assignment
• Improve dispatcher decision-making

Components of the Map Integration

To make the map feature work seamlessly, a few key components are involved:

 1. Bing Maps Integration

Dynamics 365 Field Service uses Bing Maps API for geocoding and route calculation. You’ll need a Bing Maps Key (provided by Microsoft Azure) for map rendering.

 2. Bookable Resource Locations

Each technician (bookable resource) should have a latitude and longitude value associated with their profile.

 3. Work Orders with Address Data

Work orders must have valid address information (including country, city, postal code, etc.) to be plotted on the map.

 4. Resource Scheduling Optimization (RSO) (Optional but Recommended)

This AI-based service automatically schedules the nearest and most optimal resource for a job using geospatial intelligence.

Step-by-Step Configuration Guide

Step 1: Acquire a Bing Maps API Key

1. Go to the [Azure Portal](https://portal.azure.com).

2. Search for "Bing Maps" and create a new Bing Maps Account.

3. Generate your Bing Maps API Key.

4. Copy the key for future use.

 Step 2: Set Up Bing Maps in Dynamics 365

1. Open Power Platform Admin Center.

2. Navigate to Environments > \[Your Environment] > Settings > Product > Features.

3. Scroll down to Map and Address Suggestions.

4. Paste your Bing Maps Key in the provided field.

5. Save and refresh the environment.

Step 3: Enable Latitude/Longitude Capture

1. Go to Field Service > Settings > Field Service Settings.

2. Enable the Auto Geo Code Addresses option.

3. Ensure that your address fields are correctly mapped to geolocation fields (Latitude, Longitude).

Step 4: Validate Bookable Resources

1. Go to Field Service > Resources.

2. Open each resource record and ensure a primary address is present.

3. If available, manually add latitude and longitude or use the auto-geo code feature.

Step 5: Validate Work Order Locations

1. Navigate to Field Service > Work Orders.

2. Open a work order and ensure the Service Address is valid.

3. Check if latitude and longitude are automatically populated.

Step 6: Configure the Schedule Board

1. Open the Schedule Board in Field Service.

2. Click on the Map View.

3. Use filters to show resources and work orders on the map.

4. Drag and drop work orders to the closest available resource.

Use Case Scenarios

Route Optimization

Dispatchers can minimize travel time by assigning the nearest technician using the map view.

Territory Management

Field teams can be assigned and scheduled based on regions, improving coverage and ownership.

Proximity Booking

When an urgent case is raised, the map helps find the closest available technician.

Testing & Validation Tips

• Test with dummy work orders having different addresses to verify mapping.
•  Ensure all addresses are in standardized formats for consistent geocoding.
•  Use browser tools (F12 in Chrome) to monitor any map-related API errors.

Final Thoughts

The Integrated Map Feature in Dynamics 365 Field Service is a powerful tool that transforms traditional scheduling into a smart, location-aware operation. By following the above steps, you can unlock visibility, efficiency, and productivity in your field service management process.

https://powerappbuilder.blogspot.com/2025/06/dynamics-365-field-service-configure_23.html

Published on: 6 hours ago

Dynamics 365 Business Central: How to note the records that the user has selected on the Subpage/Lines (Page.SetSelectionFilter in part)

Hi, Readers.Today I would like to share another mini tip about Business Central, how to note the records that the user has selected on the Subpage/Lines (Page.SetSelectionFilter in part) Page.SetSelectionFilter(var Record) is a very commonly used method, which can get the value currently selected by the user. Page.SetSelectionFilter(var Record): Notes the records that the user […]

https://yzhums.com/25134/

Published on: 7 hours ago

Steve Smith: Software Architecture - Episode 355

Steven Smith, also known in the developer community as Ardalis, is an entrepreneur, author, and software architect with a deep passion for building effective, maintainable software. Through his company, NimblePros, Steve helps organizations — ranging from household names like Microsoft and Quicken Loans to growing teams across industries — maximize their development potential. His clients frequently describe him as a “force multiplier,” amplifying the productivity and impact of the teams he supports.   Steve has been recognized as a Microsoft MVP for over two decades and continues to lead through education and mentorship. He’s published numerous courses on Pluralsight and Dometrain, focusing on topics like domain-driven design, software architecture, and design patterns. He also empowers developers through his mentorship platform, DevBetter.com, helping the next generation of professionals grow their careers with intention and clarity.   Topics of Discussion: [2:28] What keeps Steve excited about computer programming and software architecture? [4:42] What is software architecture? [6:18] The importance of understanding the logical components of a software system and how they interact. [7:06] Artifacts for architecture decisions. [8:52] How lightweight documentation and diagrams, like those in the C4 Model, can clarify system design without overburdening the team. [10:53] The modern architecture books that have caught Steve’s eye. [12:57] The KISS principle and keeping software architecture simple. [19:38] Clean architecture and domain-driven design principles. [22:52] Managing out-of-process dependencies and service integrations. [26:07] Adapter pattern and interface abstractions. [28:33] Decorator pattern for adding functionality. [33:14] Pipeline Architecture. [40:35] What Steve thinks the future holds for AI-driven development, what he uses it for, and the challenges of AI currently.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Programming with Palermo — New Video Podcast! Email us at [email protected]. Clear Measure, Inc. (Sponsor) “Steve Smith: .NET 8 and Architecture” - Episode 276 NimblePros  Architect Modern Web Applications with ASP.NET Core and Azure  C4 Model  “Simon Brown on Architecture for Developers - Episode 96” Fundamentals of Software Architecture, by Mark Richards & Neal Ford, summarized as a platform-agnostic, principle-driven guide   .NET Rocks! “Architecture vs. Code with Steve Smith”  .NET Rocks! “Vertical Slice Architecture with Jeremy Miller”  GoF Adapter pattern .NET API interface estimate  Decorator pattern Bus vs. Pipeline patternsBus Vs. Pipeline patterns   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

https://open.spotify.com/episode/4XmoTxEjhMezR0ovamWpqV

Published on: 9 hours ago

Copilot Studio: Detect Multiple Entity Types In A Question

In Copilot Studio you can detect multiple entity types (name, email, etc.) in a question ...

The post Copilot Studio: Detect Multiple Entity Types In A Question appeared first on Matthew Devaney.

https://www.matthewdevaney.com/copilot-studio-detect-multiple-entity-types-in-a-question/

Published on: 11 hours ago

Power BI Copilot AI Instructions: Helping Users Understand The Scope Of The Data

Continuing my series of posts on Power BI Copilot and the type of things you should be including in AI Instructions, today I want to talk about helping the end user understand the scope of the data: what data your model does contain, what data it could contain but doesn’t, and what data it could … Continue reading Power BI Copilot AI Instructions: Helping Users Understand The Scope Of The Data →

https://blog.crossjoin.co.uk/2025/06/22/power-bi-copilot-ai-instructions-helping-users-understand-the-scope-of-the-data/?utm_source=rss&utm_medium=rss&utm_campaign=power-bi-copilot-ai-instructions-helping-users-understand-the-scope-of-the-data

Published on: 16 hours ago

Low Code's Future? A2A, MCP, CUA (What the future may hold)

https://www.youtube.com/watch?v=po3hp-WKCKQ

Published on: 20 hours ago

Power BI UX Just Got Easier

https://www.youtube.com/watch?v=zF7SOU8QlbA

Published on: 21 hours ago

Get Started with Responsive Canvas App 🔥 | Complete Beginner Tutorial– EP01

https://www.youtube.com/watch?v=yjPMwrEs8xI

Published on: 21 hours ago

Why Plugin Depth Matters in Dynamics CRM

Plugin development in Dynamics CRM is one of the most advanced and intricate components, requiring deep expertise in the platform's event pipeline and a solid architectural design. Poorly designed plugins can introduce significant performance bottlenecks. A key consideration is plugin depth, which indicates the number of nested executions within a single transaction. Uncontrolled plugin depth can lead to recursive loops, increased processing time, and system instability—making its management essential in enterprise-grade solutions. 

What Is Plugin Depth?

Plugin depth is an integer value that represents the level of recursive execution or chaining of plugins. It is used internally to prevent infinite loops or overly complex recursive plugin calls.

You can access the current plugin’s depth using:

context.Depth

Why Depth Matters

Microsoft places a limit on plugin depth to avoid performance issues and infinite recursion.

• The default maximum depth is 8.
•  If the plugin execution depth exceeds this limit, the system throws an exception:

System.InvalidOperationException: Infinite loop detected in plugin execution. Depth > 8

Can Depth Be Negative?

• No, plugin depth in Dataverse cannot be negative.
• The depth is always a positive integer (starting from 1) and increases with each subsequent internal call that causes a new plugin execution.

"The plug-in execution has exceeded the maximum depth allowed of 8."

if (context.Depth > 1)

{

    // Skip execution or handle accordingly

    return;

}

if (!target.Contains("fieldName")) return;

Use Service Bus / Azure Functions for Decoupling

Instead of chaining plugins, use Azure Service Bus or Event Grid for message-based communication. For example:

• Plugin A publishes a message
• Azure Function processes it independently
• No nested plugin depth involved

5. Review and Refactor Plugin Design

Ask yourself:

•  Is this logic better handled in a workflow, Power Automate, or custom action?
•  Can the logic be moved to a single place to reduce duplication?

Best Practices for Plugin Development in Dynamics 365

Designing efficient and reliable plugins in Dynamics 365 requires a careful approach to prevent performance issues and unintended behaviors. Here are some essential best practices to follow when working with plugins:

1. Keep Plugin Depth Minimal (Ideally ≤ 3)

The deeper the plugin chain, the higher the risk of recursion and performance degradation. Limit depth to avoid exceeding Dynamics 365's maximum limit (depth 8) and to keep execution fast and predictable.

2. Use Flags or Shared Variables to Prevent Reprocessing

Plugins may execute multiple times during a transaction. Use custom flags or `context.SharedVariables` to ensure your plugin doesn’t reprocess the same logic unnecessarily.

3. Leverage Asynchronous Mode for Long-Running Operations

Tasks like external API calls or heavy data processing should be handled asynchronously. This prevents blocking the main transaction pipeline and improves overall responsiveness.

4. Avoid Circular Plugin Calls

Circular logic—where Plugin A triggers Plugin B and B triggers A—can lead to infinite loops and application crashes. Carefully audit dependencies between plugins to avoid such recursive chains.

5. Offload Heavy Business Logic to Azure Functions

For complex processing, consider using Azure Functions or Logic Apps. This approach decouples plugin logic, increases maintainability, and supports better scalability.

6. Use Pre-Validation and Pre-Operation Stages Strategically

Choose the appropriate plugin stage for your logic:

• Use Pre-Validation for early validation checks that can halt execution.
• Use Pre-Operation to modify data before it’s committed.
• This keeps processing efficient and avoids unnecessary operations.

Conclusion: Managing Plugin Depth for Long-Term Success

Understanding and controlling plugin depth in Dynamics 365 isn’t just a technical recommendation — it’s a critical best practice for building scalable, performant, and maintainable CRM solutions.

Poor plugin design can quickly spiral into recursive loops, long execution times, and unexpected errors that are difficult to debug and resolve. But with a thoughtful approach — limiting plugin depth, using shared variables, leveraging asynchronous execution, and offloading complex logic to Azure Functions — you can ensure your customizations are both powerful and stable.

Whether you're developing for a small deployment or an enterprise-grade system, plugin depth should never be an afterthought. It’s a foundational pillar of efficient plugin architecture.

Build smart. Think ahead. Design with depth in mind.

https://powerappbuilder.blogspot.com/2025/06/why-plugin-depth-matters-in-dynamics-crm.html

Published on: 1 day ago

Exploring AI Perspectives: Optimists, Deniers, and the Angry Camp

https://www.youtube.com/watch?v=FgLmZwjicZA

Published on: 1 day ago

On-Demand Translation in Dynamics 365 CRM | Powered by Azure Translator

https://www.youtube.com/watch?v=N5hteVozyuw

Published on: 1 day ago

Microsoft 365 Copilot Services Outsourcing: Smartest Move for Business Growth!

In an era where AI is reshaping how businesses operate, the race to adopt the latest technologies is intensifying. One of the most exciting developments in this space is Microsoft’s Copilot ecosystem, from Copilot Studio to Copilot Agents and now deeply integrated across Dynamics 365 and Power Platform. But here’s the challenge Building and embedding… Read More »

The post Microsoft 365 Copilot Services Outsourcing: Smartest Move for Business Growth! first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

https://www.inogic.com/blog/2025/06/microsoft-365-copilot-services-outsourcing-smartest-move-for-business-growth/

Published on: 2 days ago

Dynamics 365 Field Service : Customize a schedule board

The Schedule Board in Microsoft Dynamics 365 Field Service is a powerful tool that provides dispatchers and field service managers a visual interface to assign and manage work orders efficiently. However, every business operates differently, and the default configuration might not suit every organization’s needs.

In this blog, we’ll walk you through how to customize the schedule board to align with your operational workflows, improve usability, and enhance field technician productivity.

What is the Schedule Board?

The Schedule Board is a dispatching interface used to manage bookings for resources (usually field technicians) in real time. It enables dispatchers to:

• View available and booked resources
• Drag and drop work orders to assign them
• See location data for resources and jobs (map view)
• Track job statuses visually
• Monitor travel time and availability

By default, the board shows:

• Resources on the left
• Time-based booking slots in the center
• Map and details pane on the right

But with customization, you can make it work your way.

Why Customize the Schedule Board?

Every organization may have different dispatching needs. Customization helps:

• Improve dispatcher efficiency
• Show only relevant work orders or technicians
• Prioritize high-value jobs visually
• Integrate with custom business logic (e.g., KPIs or alerts)

Types of Customizations

Here’s a breakdown of the main customization areas:

 1. Schedule Board Tabs

Tabs let you create different views of the board for different teams, regions, or work types.

Use Case: Create separate tabs for North and South regions, or one for Installations and another for Repairs.

How to customize:

•  Go to Resource Scheduling > Settings > Schedule Board Settings
•  Click + New to create a new tab
•  Filter resources or bookings using query builders
•  Set default map locations or working hours

2. Resource Cell Customization

Customize what information is shown next to each technician/resource.

Use Case: Show certifications, territory, or custom KPIs next to the technician name.

How to customize:

• Open the Schedule Board tab
• Select Settings > Resource Cell Template
• Use Liquid or JavaScript to define what data to display

3. Booking Template Customization

Modify how bookings (colored blocks) appear on the board.

Use Case: Change the color of bookings based on work order priority or SLA.

How to customize:

• Navigate to Booking Template
• Edit the HTML/CSS template for booking display
• You can use custom logic or calculated fields for color coding

 4. Map Customization

Adjust what is displayed in the map view (technician location, work orders, traffic, etc.).

Use Case: Show only high-priority bookings on the map.

How to customize:

• Use map filters in the Schedule Board tab settings
• Toggle options like traffic overlay or resource icons

 5. Filter Panel Customization

Add filters for dispatchers to quickly narrow down the list of resources or bookings.

Use Case: Add a filter for skill sets or territories.

How to customize:

• Open the tab and select Settings > Filter Layout
• Use FetchXML to define custom filters

 6. Custom JavaScript Extensions

• Inject custom behavior into the schedule board (advanced use).
• Use Case: Trigger alerts when high-priority bookings are overdue.

How to customize:

•  Use the OnRecordSelect or OnBookingChanged JavaScript hooks
•  Extend the Schedule Board via the Schedule Board Extensibility SDK

Real-Life Example: Customizing for Emergency Dispatch

Scenario: A company offers 24/7 emergency HVAC repair services. Dispatchers need to:

•  Instantly spot unassigned emergency work orders
•  View technician overtime availability
•  Prioritize high-SLA jobs

Customization Steps:

1. Create a new tab: "Emergency Dispatch"

2. Filter work orders where `Priority = High` and `Status = Open`

3. Customize booking templates to show SLA countdown

4. Color-code bookings: red for overdue, yellow for 1 hour left

5. Add a filter panel: SLA Time Remaining, Region

6. Add a JavaScript extension: pop-up alert if a job is unassigned past 10 mins

Final Thoughts

Customizing the Dynamics 365 Field Service Schedule Board transforms it from a generic tool to a tailored dispatching solution. Whether it's through filtering, visual cues, map settings, or advanced scripting, each tweak helps improve productivity and decision-making.

https://powerappbuilder.blogspot.com/2025/06/dynamics-365-field-service-customize.html

Published on: 2 days ago

Convert PowerShell Script to EXE in Windows

https://www.youtube.com/watch?v=cJ9WOzPywAI

Published on: 2 days ago

Dynamics 365 Field Service : Configure the Requirements panel

In Dynamics 365 Field Service, Requirement records represent the work that needs to be done—such as a maintenance task, installation, or inspection. These requirements are often associated with Work Orders and are visualized in the Schedule Board.

The Requirements Panel in the Schedule Board is a powerful UI feature that allows dispatchers to view, filter, and interact with these unscheduled work requirements. By configuring the Requirements Panel, organizations can tailor the dispatcher experience and make their scheduling process more efficient.

Let’s dive into how to configure the Requirements Panel in Dynamics 365 Field Service and tailor it to suit your dispatching needs.

 What Is the Requirements Panel?

The Requirements Panel is a sidebar on the Schedule Board that displays unscheduled Resource Requirements. It includes:

•  Filters (Territory, Time range, etc.)
•  Requirement cards (summarized info)
•  Search options
•  Drag-and-drop to assign to resources

By customizing this panel, you improve:

• Dispatcher efficiency
•  Work visibility
•  Resource utilization

 How to Configure the Requirements Panel

 Step 1: Navigate to the Schedule Board

1. Go to Field Service > Schedule Board.

2. Select the Schedule Board Tab you want to configure.

3. Click on the ellipsis (…) > Settings to open board settings.

Step 2: Configure the Requirements Tab

Inside the board settings, locate the "Requirements Tab" configuration. Here you’ll find several customization options:

Requirement Views

•  You can define which view of the Requirement entity to use.
•  Example: “Open Requirements This Week”
•  You can create a custom system view in the Advanced Find or Power Apps Maker and use it here.

Filters Configuration

 Enable or disable filters like:

• Territory
•  Organizational Unit
•   Priority
•  Date range

 These filters help narrow down the list based on dispatcher focus.

Requirement Card Configuration

You can customize the fields that show up on each requirement card, such as:

•  Customer name
•  Requirement type
•  Service task
•  Status
•  Priority

This is done via Requirement Card Templates or via JavaScript customization (for advanced users).

Step 3: Advanced Configuration with Custom Views or Fields

Want to go further?

You can:

•  Add custom fields to the Requirement entity
•  Add those fields to the system views
•  Use those fields as part of card or filter display

For example, if you add a field like “Requires Special Equipment”, you can create a view to only show such requirements and display this field on the card.

Best Practices

Here are some best practices for configuring the Requirements Panel:

Keep it Clean

• Don’t overload the cards or filters. Use only fields that help with dispatching decisions.

Use Business-Centric Views

• Create views that align with your business logic—e.g., "High Priority Unscheduled Requests".

Group by Territory or Skills

• Use filters like Territory or Skill requirement to assign the right technician quickly.

Test with Dispatchers

• Always test changes with end users to make sure the panel supports their daily workflow.

Real-World Example

Imagine a national HVAC repair company using Dynamics 365 Field Service:

• They configure the Requirements Panel to only show emergency repair jobs for the current week.
• Cards show the customer name, issue type, and priority.
• Dispatchers filter by region (Territory) and technician skillset.
• Using drag-and-drop, they assign work to technicians directly from the panel.

This setup saves hours of manual planning and improves service delivery speed.

https://powerappbuilder.blogspot.com/2025/06/dynamics-365-field-service-configure_97.html

Published on: 2 days ago

Learning Path : Create agents in Microsoft Copilot Studio

If you’re a beginner in Microsoft Copolit Studio (MCS), Did you know that there is a learning path available : Create agents in Microsoft Copilot Studio Where you can learn how to create custom agents in Copilot Studio and practice your skills with a guided project. You can also take the MCS Assessment Test to […]

https://rajeevpentyala.com/2025/06/21/learning-path-create-agents-in-microsoft-copilot-studio/

Published on: 2 days ago

Dynamics 365 Field Service : Configure and manage schedule boards, including customizing views

In the world of field service management, scheduling is everything. You need the right technician, at the right time, with the right tools and skills — delivered efficiently to meet customer expectations. That’s where the Schedule Board in Dynamics 365 Field Service comes in.

This powerful visual tool allows dispatchers and schedulers to view, manage, and optimize technician schedules, bookings, and resources in real-time. But beyond its out-of-the-box capabilities, the Schedule Board can be deeply customized to match your organization’s workflows and preferences.

In this post, we’ll explore:

•  What the Schedule Board is
•  How to configure it
•  How to manage resources and bookings
•  Customization options for different views

What Is the Schedule Board?

The Schedule Board is a core component of Resource Scheduling in Dynamics 365 Field Service. It's a drag-and-drop, map-enabled, timeline-based interface that provides a consolidated view of:

•  Resources (technicians, vehicles, equipment)
•  Bookings (work orders, cases, custom entities)
•  Resource availability
•  Travel time and route optimization

The Schedule Board helps dispatchers allocate the right field resources to work orders quickly and efficiently.

How to Configure the Schedule Board

 1. Access the Schedule Board

• Go to:
• Field Service > Schedule Board

You’ll see a default view of resources grouped by territory or organizational unit.

 2. Understand the Layout

•  Left Panel: List of available resources
•  Top Timeline: Bookings across time slots
•  Map Panel (optional): Route and work location visualization
•  Filter Panel: For narrowing down resources by territory, role, skills, etc.

 3. Configure Settings (Admin/Dispatcher Role)

• You can access the Schedule Board settings by clicking the gear icon ⚙️ on the board or navigating to:
• > Resource Scheduling > Administration > Schedule Board Settings

From there, you can:

•  Define filters (e.g., work order types, territories, skills)
•  Configure resource cell templates
•  Enable/disable booking alerts
•  Set map settings and colors
•  Set default time zone and refresh rates

Customizing Views on the Schedule Board

Customization lets you tailor the board for different dispatcher roles or regional needs.

1. Create a Custom Schedule Board Tab

Each tab represents a different view. You can define:

• Resource filters (e.g., only show North Territory)
• Booking requirements filters
• Map configurations
• Time ranges (e.g., work week, day view)

Steps to Create:

•  Open Schedule Board
•  Click + New Tab
•  Name the tab (e.g., "East Zone Dispatcher")
•  Define filter criteria
•  Save and test your view

 2. Customize Resource Cards

Resource cards show vital information about the technician:

•  Name
•  Roles
•  Availability
•  Skills

You can modify the resource template using custom JavaScript (within limits) or change layout via Resource Cell Template settings in Schedule Board Settings.

 3. Customize Booking Templates

Booking templates define how a booking appears on the board. You can change:

• Text format
• Color (based on status or priority)
• Icons (e.g., warning, alerts)

This helps dispatchers quickly identify urgent or problematic bookings.

 4. Use Booking Alerts

Enable alerts to notify schedulers when:

•  A booking overlaps with another
•  A technician lacks the required skill
•  A work order is not completed in time

Alerts improve visibility into scheduling conflicts or risks.

Conclusion

The Schedule Board in Dynamics 365 Field Service is more than a calendar — it’s a dynamic, customizable dispatching hub that can be tailored to the specific needs of your organization. With the right configuration and custom views, you can empower your dispatchers to manage resources with precision, reduce downtime, and delight your customers.

https://powerappbuilder.blogspot.com/2025/06/dynamics-365-field-service-configure_21.html

Published on: 2 days ago

Reflections from #EPPC25: Building a 10× Future with Autonomous Agents

This week in Vienna, I had the privilege of attending the European Power Platform Conference (#EPPC25)—a gathering that not only showcased the latest innovations from Microsoft but also sparked deep conversations about the future of work, the role of AI, and how we as professionals can prepare for what’s next. A powerful message was delivered […]

https://carstengroth.wordpress.com/2025/06/20/reflections-from-eppc25-building-a-10x-future-with-autonomous-agents/

Published on: 2 days ago

Microsoft MVP Ana Ines Urrutia prepares for PPCC25!

https://www.youtube.com/watch?v=re7Stplvrjs

Published on: 2 days ago

Dynamics 365 Field Service : Schedule work orders by using the schedule board and schedule assistant

Field service operations rely heavily on effective scheduling to ensure the right technician is assigned to the right job at the right time. In Microsoft Dynamics 365 Field Service, two powerful tools help dispatchers and schedulers optimize work order assignments: Schedule Board and Schedule Assistant.

Let’s dive into what these tools are, how they work, and how you can use them effectively to streamline your field service operations.

What Is a Work Order in Field Service?

A work order is a central component of Field Service. It represents a job or service that needs to be performed at a customer location. It includes:

•  Customer details
•  Incident types (the kind of service to be performed)
•  Required products, services, and skills
•  Preferred time windows

Once created, work orders need to be scheduled to technicians or resources who will complete the job.

The Schedule Board: Your Dispatching Command Center

The Schedule Board is a visual, drag-and-drop tool that gives dispatchers a centralized view of:

•  Available technicians (resources)
•  Work orders waiting to be assigned
•  Travel routes and statuses
•  Technician availability and working hours

 Key Features of the Schedule Board:

|

 How to Use the Schedule Board:

1. Navigate to Field Service > Schedule Board.

2. Use the filters to select the region or territory you’re managing.

3. Unscheduled work orders appear on the Unscheduled Panel.

4. Drag and drop the work order onto a resource’s calendar.

5. Save the booking, and the technician is now scheduled.

 Schedule Assistant: Smart Scheduling Made Easy

• If you want the system to help you choose the best resource for a job, use the Schedule Assistant.
• This tool uses parameters like skills, location, availability, work hours, and resource type to recommend the best technician automatically.

Key Benefits:

•  Reduces manual scheduling effort
•  Ensures resource matching based on required skills
•  Optimizes travel time and scheduling gaps
•  Improves customer satisfaction through better time window adherence

How to Use the Schedule Assistant:

1. Open a work order.

2. Click Book (or use the Schedule Assistant button from the ribbon).

3. The assistant analyzes the job requirements and lists the best matching technicians.

4. It shows recommended time slots, estimated travel times, and booking overlaps.

5. Choose one and click Book & Exit to confirm.

Schedule Board vs. Schedule Assistant: When to Use Which?

•  Configure resource characteristics (skills, territories) properly for better assistant results.
•  Use resource preferences to prioritize certain technicians for specific customers.
•  Implement travel time calculations to optimize routes.
•  Customize booking rules to enforce business logic (e.g., must have safety certification).

Final Thoughts

Efficient scheduling is critical to the success of field service operations. Whether you prefer a visual, hands-on approach with the Schedule Board, or a smart, AI-assisted approach using the Schedule Assistant, Dynamics 365 Field Service equips you with the tools to:

•  Reduce technician idle time
•  Improve first-time fix rates
•  Enhance customer satisfaction
•  Optimize operational efficiency

By mastering these tools, your dispatchers can make informed decisions faster, resulting in smoother field operations and better service outcomes.

https://powerappbuilder.blogspot.com/2025/06/dynamics-365-field-service-schedule.html

Published on: 2 days ago

Microsoft Dataverse – Build Agents with Azure Databricks as your knowledge source

We are announcing the ability to connect Azure Databricks to Microsoft Power Platform to create canvas apps in Power Apps using Databricks data in a no-code way, and to use Azure Databricks as a knowledge source to ground your Copilot agents for intelligent, data-driven responses. This feature will reach general availability on July 19, 2025. How does this affect me? The new Databricks Connector that links Azure Databricks to Power Platform provides users: Canvas app integration: Build apps in Power Apps with real-time Azure Databricks data to ensure current and accurate information. Interact with your data through natural language, backed by Databricks’ powerful processing engine. Real-time CRUD Support: Enable seamless CRUD (create, read, update, delete) operations on Azure Databricks data directly within Power Apps. Knowledge Source for Copilot Agents: Add Azure Databricks datasets and tables that can be curated by developers and analysts as a Knowledge Source, enabling Copilot Agents to answer natural language queries using structured Databricks data. Low-code availability: A scalable, real-time integration point between Databricks and Microsoft’s low-code ecosystem, accelerating insights and reducing operational overhead. What action do I need to take? This message is for awareness and no action is required. The Azure Databricks connector is currently in preview. To start using Azure Databricks as a Knowledge Source before general availability: Connect your Databricks workspace to Power Platform using the Azure Databricks Connector. Add your Databricks tables as Knowledge Sources in Copilot Studio. Configure and test your Copilot Agent to respond to natural language queries grounded in Databricks data. If you would like more information on this feature, please visit Azure Databricks – Connectors. Message ID: MC1098956

The post Microsoft Dataverse – Build Agents with Azure Databricks as your knowledge source appeared first on M365 Admin.

https://m365admin.handsontek.net/microsoft-dataverse-build-agents-azure-databricks-knowledge-source/

Published on: 2 days ago