Initialising the component

To add a component to your webpage, you can copy the following code and edit it as per your component:

{% include '<<web template name>>' <<parameter 1>>: '<<value>>' <<paramter 2>>: '<<value>>' %}

For instance, to include the component (with default) created in this you would use the following code:

{% include 'alertscomponent' %}

Defining the component

The liquid code of your “alertscomponent” component will be as follows:

<div id="{{ _id | default: 'dvAlertInfo' }}" class="alert {{ _class | default: 'alert-info' }}" role="alert">
  {{ _content | default: 'Default info alert content.'}}
</div>
{% manifest %} 
    { 
    "type": "Functional", 
    "displayName": "Alerts Component", 
    "description": "This returns the alerts html based on the class and the content", 
    "tables": ["alerts"], <!--This component can be updated based on the table schema you would like to use in current environment.-->
    "params": [{ 
        "id": "_id", 
        "displayName": "Alert id", 
        "description": "Element id of the alert div" 
        },{ 
        "id": "_class", 
        "displayName": "Alert class", 
        "description": "Alert type class of the alert div" 
        },{ 
        "id": "_content", 
        "displayName": "Alert content", 
        "description": "Content of the alert div" 
        }] 
    } 
{% endmanifest %}

In the dynamics environment, you’ll be creating the component with following attribute:

Including in web page template

The component created is reusable and can be initialised at multiple occurances. Since, it is a parameterised component it’s behaviour may vary depending upon the parameters provided upon each instance as shown below:

<!-- This should display the default alerts component -->
{% include 'alertscomponent' %}

<!-- This should display the success alerts component with custom success message -->
{% include 'alertscomponent' _id: 'dvAlertSuccess' _class: 'alert-success' _content: 'This is the success content.' %}

<!-- This should display the danger alerts component with custom danger message -->
{% include 'alertscomponent' _id: 'dvAlertDanger' _class: 'alert-danger' _content: 'This is the danger content.' %}

<!-- This should display the warning alerts component with custom warning message -->
{% include 'alertscomponent' _id: 'dvAlertWarning' _class: 'alert-warning' _content: 'This is the warning content.' %}

Output

The output of the following page should as follows:

The post Power Pages – Web templates as components appeared first on Dev Beard Guy.

Occasionally, the customer service agent has a requirement of creating a case manually. By adding the related information such as the subject, origin, priority, and the customer against which it needs to be recorded.

There are two OOTB approaches available for manual case creation.

• Using a case page
• Using quick create form

Using case page

The Case page is the most commonly used method for entering cases into Dynamics 365. As a case is entered, the agent who’s entering it specifies details about the case, like the case title, customer, case origin, and so on.

This is the most common approach for capturing the case manually which constitutes of the following steps:

1. Navigate to the Case page.
2. Provide related information on the Case page.
3. Save & Exit.

Using quick create form

The Quick Create: Case dialog box is a trimmed-down version of the Case page. It has only the most important fields for the case entity. 

This dialog box is used to quickly enter case information, to save time. You also use this dialog box when you’re creating a case in the context of another record. For example, if you add a case directly from an account in Dynamics 365, you’ll use the Quick Create: Case dialog box.

Quick Create dialog boxes can be accessed from the top navigation bar in the application, or from the related panel or an attached sub-grid on a parent record. Although a Quick Create dialog box isn’t available by default for every entity, it’s available for the case entity. Therefore, when you add a case from a related record, you use the Quick Create: Case dialog box.

This is suitable when creating a case against a related Parent record such as a Contact or Account record. The steps to capture a case using the quick create form are as follows:

1. Open the Account page.
2. Navigate to the related record, and select the Case tab.
3. Click on the New Case button to open the Quick Create: Case dialog box.
4. Provide related information on the Quick Create: Case.
5. Save & Exit.

The information is fetched from Microsoft documentation.

The post Dynamics 365 Customer Service – Manual Case Creation appeared first on Dev Beard Guy.

In today’s fast-paced business environment, the successful management of field service operations is critical for organizations across various industries. Dynamics 365 Field Service, a part of the Microsoft Power Platform, is a powerful solution designed to optimize and streamline field service operations. In this post, we will explore the key steps to set up Dynamics 365 Field Service and how it can revolutionize your field operations, enhancing productivity, customer satisfaction, and overall efficiency.

What is Dynamics 365 Field Service?

Dynamics 365 Field Service is an end-to-end solution that enables organizations to manage and coordinate field service activities seamlessly. Whether you provide installation, maintenance, repairs, or other on-site services, this platform equips your team with the necessary tools and insights to deliver exceptional field service experiences. By automating processes, enabling real-time communication, and leveraging data-driven decision-making, Dynamics 365 Field Service empowers your organization to deliver efficient, personalized, and proactive field services.

Setting Up Dynamics 365 Field Service: A Step-by-Step Guide

Step 1: Assessing Business Requirements

Before diving into the implementation process, it is crucial to understand your organization’s specific field service needs and objectives. Conduct a thorough assessment of your existing processes, service level agreements, technician capabilities, and customer expectations. This step will lay the foundation for a successful Dynamics 365 Field Service setup tailored to your unique business requirements.

Step 2: Licensing and Subscriptions

Ensure that your organization has the necessary licenses and subscriptions for Dynamics 365 Field Service. Depending on your needs, you might require licenses for Dynamics 365, Field Service, and additional modules like Resource Scheduling Optimization (RSO) for advanced scheduling capabilities.

Step 3: Integration and Data Migration

To leverage the full potential of Dynamics 365 Field Service, integrate it with your existing systems such as customer relationship management (CRM), enterprise resource planning (ERP), and asset management systems. Smooth data migration from your legacy systems to Dynamics 365 will ensure a seamless transition without losing critical information.

Step 4: Configure Field Service Settings

In the Dynamics 365 administration portal, configure Field Service settings to align with your business requirements. Customize work order types, service territories, incident types, and other field service-related entities to match your specific operations.

Step 5: Set Up Resource Scheduling

Resource scheduling is a core aspect of Dynamics 365 Field Service. Enable the resource scheduling optimization feature to efficiently assign tasks to the right technicians based on their skill set, availability, location, and other criteria. This optimization helps minimize travel time, maximize resource utilization, and improve service response times.

Step 6: Mobile Enablement

Equip your field technicians with mobile devices and configure the Dynamics 365 Field Service mobile app. The mobile app enables technicians to access work orders, customer information, service history, and real-time updates on the go. This mobile enablement enhances productivity and allows for seamless communication between field technicians and the back-office team.

Step 7: Automation and AI Integration

Leverage the power of automation and artificial intelligence (AI) to enhance field service operations. Integrate IoT devices to monitor and proactively address equipment health, enabling predictive maintenance. Utilize AI-driven analytics to optimize schedules, detect potential issues, and provide valuable insights for continuous improvement.

Step 8: Training and Adoption

For a successful implementation, conduct comprehensive training sessions to familiarize your team with Dynamics 365 Field Service. Empower them to use the platform effectively, understand its capabilities, and embrace the digital transformation it brings to your field service operations.

Conclusion

Dynamics 365 Field Service is a game-changer for organizations seeking to optimize their field service operations. By setting up and harnessing the power of this comprehensive solution, you can streamline processes, improve resource utilization, boost customer satisfaction, and elevate your overall service quality. Embrace the digital revolution in field services with Dynamics 365, and pave the way for a more efficient and successful future for your organization.

The post Setting Up Dynamics 365 Field Service: Streamlining Field Operations for Optimal Efficiency appeared first on Dev Beard Guy.

Power Apps Component Framework (PCF) empowers developers to build custom controls that seamlessly integrate with Microsoft Power Apps, Dynamics 365, and other Power Platform applications. These controls enhance user experiences by providing tailored functionalities and visual elements. In this blog, we will guide you through the process of creating and setting up a PCF control using Visual Studio 2019, Microsoft’s powerful integrated development environment (IDE). Let’s dive in!

What is PCF (Power Apps Component Framework)?

The Power Apps Component Framework (PCF) allows developers to create custom controls using modern web development technologies such as HTML, CSS, and TypeScript. These controls can be directly used within canvas apps, model-driven apps, and Dynamics 365 forms. By leveraging PCF, developers can extend the native capabilities of Power Apps and tailor solutions to meet specific business needs effectively.

Prerequisites:

Before we begin, ensure you have the following prerequisites installed on your machine:

1. Visual Studio 2019: You can download the latest version of Visual Studio 2019 from the official Microsoft website.
2. Node.js: PCF development requires Node.js to manage dependencies and build processes. Download and install the latest version from the Node.js website.
3. PCF CLI: Install the Power Apps CLI (PCF CLI) using npm, which comes with Node.js. Open your terminal or command prompt and run the following command:

npm install -g powerapps-cli

Creating a PCF Project in Visual Studio 2019:

Step 1: Launch Visual Studio 2019

Open Visual Studio 2019 and click on “Create a new project.”

Step 2: Select “PCF Control Library”

In the search bar, type “PCF” to filter the project templates. Select “PCF Control Library” from the list of project templates.

Step 3: Provide Project Details

Enter the project name and choose a location where the project files will be stored. Click “Create” to proceed.

Step 4: Configure the PCF Control

Visual Studio will prompt you to configure the PCF control. Provide the required details, such as the control name, namespace, and version.

Step 5: Writing Code for PCF Control

Visual Studio will generate the necessary files for your PCF control project. You’ll find TypeScript files, manifest files, and other related resources.

The primary code file is the TypeScript file (index.ts) that represents the logic and behavior of your control. You can use HTML and CSS files to define the control’s visual aspects.

Step 6: Build the PCF Control

Once you’ve written your code, it’s time to build the PCF control. Open the terminal in Visual Studio and execute the following command:

msbuild /t:build

This command will compile the TypeScript files and generate the necessary artifacts for the PCF control.

Setting Up the Control in Power Apps:

Step 1: Package the PCF Control

After building the control successfully, use the PCF CLI to package it. In the terminal, navigate to the root directory of your PCF control project and run the following command:

pac pcf push

This command will create a managed solution (.zip) file containing the PCF control and its related metadata.

Step 2: Import the Solution in Power Apps

In Power Apps, navigate to the “Solutions” section and import the managed solution (.zip) you created in the previous step.

Step 3: Add the PCF Control to a Form

Now that the solution is imported, go to the desired form where you want to use the PCF control. Edit the form and add the custom control to the desired section.

Step 4: Publish the Changes

Save and publish the changes you made to the form.

Conclusion

In this blog, we explored the process of creating and setting up a PCF control using Visual Studio 2019. The Power Apps Component Framework allows developers to extend the capabilities of Power Apps and create customized, powerful controls for their applications. By following the steps outlined above, you can now start building your own PCF controls to enhance user experiences and meet specific business requirements. Happy coding!

The post Create and Setup the PCF Control Using Visual Studio 2019 appeared first on Dev Beard Guy.

In today’s fast-paced world of application development, efficient tools play a crucial role in streamlining the development process. For Microsoft Power Platform developers working with Dataverse, the Power Platform CLI (Command Line Interface) is an invaluable tool that enables seamless management of solutions, components, and other resources. In this blog, we’ll explore the benefits and features of the Power Platform CLI and guide you through the process of downloading Dataverse Development Tools using this powerful command-line tool.

Understanding Power Platform CLI

The Power Platform CLI is a cross-platform command-line interface designed to empower developers with greater flexibility and control over their Dataverse environment. It enables you to automate tasks, build continuous integration/continuous deployment (CI/CD) pipelines, and manage various components like solutions, apps, entities, and more.

Advantages of Power Platform CLI

1. Cross-Platform Compatibility: The Power Platform CLI works on Windows, macOS, and Linux systems, making it a versatile choice for developers using various operating systems.
2. Automation Capabilities: With the CLI, you can automate repetitive tasks, reducing manual errors and improving efficiency. This is especially valuable in complex development scenarios or large-scale projects.
3. Integration with CI/CD Pipelines: The CLI facilitates integration with popular CI/CD tools like Azure DevOps, GitHub Actions, and Jenkins, allowing you to create seamless deployment pipelines for your Dataverse solutions.
4. Version Control Support: By leveraging the CLI, developers can easily manage version control for their solutions, enabling them to roll back changes and collaborate effectively within a team.
5. Scripting and Extensibility: The CLI’s scripting capabilities let developers create custom commands and extensions tailored to their specific needs, enhancing the development experience further.

Downloading Dataverse Development Tools with Power Platform CLI

To download the Dataverse Development Tools using the Power Platform CLI, follow these simple steps:

Step 1: Install Power Platform CLI

If you haven’t already installed the Power Platform CLI on your machine, you can do so by following the official Microsoft documentation. The installation process differs slightly based on your operating system, but it generally involves using package managers like npm (for Node.js) or Homebrew (for macOS).

Step 2: Authenticate with Dataverse

After installing the CLI, open your terminal or command prompt and use the “power” command to connect your CLI with your Dataverse environment. You’ll need to provide your Dataverse credentials to authenticate successfully.

power login

Step 3: Download Dataverse Development Tools

With the CLI authenticated, you can now proceed to download the Dataverse Development Tools. Use the following command:

pac install latest

The command above fetches and installs the latest version of the Dataverse Development Tools, which includes various commands for managing Dataverse solutions, apps, entities, web resources, and other components.

Step 4: Verify Installation

To ensure that the installation was successful, you can run the following command to check the version of the installed tools:

pac --version

Conclusion

The Power Platform CLI is a powerful companion for developers working with Microsoft Dataverse. Its cross-platform capabilities, automation support, and integration with CI/CD pipelines make it an essential tool for efficient and streamlined development workflows. By downloading the Dataverse Development Tools using the Power Platform CLI, you gain access to a wide array of commands to manage your Dataverse solutions effectively.

As you delve deeper into your Dataverse development journey, don’t forget to explore the various features and possibilities offered by the Power Platform CLI. By mastering this command-line interface, you’ll significantly enhance your productivity and deliver high-quality solutions for your organization or clients. Happy coding!

The post Download Dataverse Development Tools with Power Platform CLI appeared first on Dev Beard Guy.

Sometimes, a case might be the result of an activity like an email, phone call, or task. For example, a support agent might receive an email request for service directly from a customer. In these situations, you can convert activities directly to Dynamics 365 case records. The record creation and update rules in Dynamics 365 are used to automatically convert specific activities to Dynamics 365 records. This conversion can also be done manually on an individual record.

 Note

The next unit will cover the automatic creation of cases from activity records.

Out of the box, the following types of Dynamics 365 activities can be converted to cases:

• Appointments
• Campaign Responses
• E-mails
• Faxes
• Letters
• Phone Calls
• Service Activities
• Tasks
• Social Activities

Any custom activities that are created for an organization can also be converted to cases. For example, an organization might create a custom activity named SMS messages that’s used to work with text messages. These activities can also be converted to cases.

From within a specific activity, select the Convert To button on the command bar. You can then select whether to convert the activity to an opportunity or a case.

After you select To Case, the Convert to Case page appears. This page provides more information and lets you do things like close the activity as finished.

The post D365 Customer Service – Converting activity records to cases appeared first on Dev Beard Guy.

Today, we’ll look at a few of the design patterns using C# and explore their possibilities in application development. C# is a versatile and powerful programming language used for developing a wide range of software applications. One of the key aspects that contribute to the success of any software project is its design. In this blog post, we will delve into the world of C# design patterns, exploring their significance, common types, and how they can greatly enhance the quality and maintainability of your code.

Understanding Design Patterns: Design patterns are reusable solutions to common programming problems that arise during software development. They provide a structured approach to design, promoting code organization, flexibility, and extensibility. Design patterns encapsulate best practices and proven architectural principles, making them invaluable tools for any C# developer.

Types of Design Patterns in C#:

1. Creational Patterns:
   • Singleton Pattern: Ensures a class has only one instance and provides a global point of access to it.
   • Factory Pattern: Encapsulates object creation, allowing the client to interact with objects without knowing their specific classes.
   • Builder Pattern: Separates the construction of complex objects from their representation, allowing the same construction process to create different representations.
2. Structural Patterns:
   • Adapter Pattern: Converts the interface of one class into another interface that clients expect.
   • Decorator Pattern: Dynamically adds responsibilities to an object by wrapping it in an object of a decorator class.
   • Composite Pattern: Treats a group of objects as a single entity, allowing clients to interact with individual objects or the entire hierarchy.
3. Behavioral Patterns:
   • Observer Pattern: Defines a one-to-many dependency between objects, ensuring that changes in one object notify and update dependent objects automatically.
   • Strategy Pattern: Defines a family of algorithms, encapsulating each one and making them interchangeable within the same context.
   • Command Pattern: Encapsulates a request as an object, allowing clients to parameterize clients with queues, requests, or operations.

Benefits of Using C# Design Patterns:

• Code Reusability: Design patterns promote code reusability by providing well-defined solutions to common problems, saving time and effort in future development.
• Maintainability: Patterns enhance code organization, making it easier to understand and modify, leading to better maintainability and reduced bugs.
• Scalability: Using design patterns enables scalability as systems can be expanded by adding new components without impacting existing code.
• Collaboration: Patterns establish a common language and understanding among developers, facilitating effective collaboration within a team.
• Performance: Properly implemented patterns can improve system performance by optimizing code structure and reducing redundancy.

Hence we can say that design patterns offer a powerful set of tools to improve the quality, flexibility, and maintainability of your software projects. By leveraging proven architectural principles and best practices, you can enhance code organization, reusability, and scalability. Understanding the different types of design patterns and their applications allows you to select the most appropriate patterns for your specific development needs. Embrace the power of C# design patterns and take your software development skills to the next level.

The post C# Design Patterns appeared first on Dev Beard Guy.