Use icons in model driven views

The content discusses how to add icons to a record view, enhancing user experience by indicating timer status visually. By uploading icons as web resources and using TypeScript logic, the script determines whether to display a "play" or "pause" icon based on the is timer active field value.

Use MS Graph in Plugins

To use MS Graph in plugins, set up Plugin Packages for NuGet integration. Create an app registration in Azure with necessary API permissions and a client secret. Implement a GraphHandler for authentication using the Microsoft.Graph NuGet Package, and facilitate API calls like deleting calendar items through this handler.

Use Plugin Package

Plugin Packages allow the addition of NuGet Packages, enhancing project capabilities beyond normal Plugins. To initiate a project, use the Microsoft Power Platform CLI (PAC). After coding, register the package through XrmToolBox. For updates, rebuild the solution first. Debugging is facilitated by the Plugin Trace Viewer in XrmToolBox.

Make ribbon button visible depending on parent form

To hide custom ribbon buttons in Model Driven Apps, you can create an enable rule using a function called "HideBtnSubgrid." This function requires three parameters: primary control, entity name, and form name. It checks for the form context, validates the entity, and determines if the button should be hidden based on the form name.

Tools you need to have in your XrmToolBox for Plugin Development

The post discusses tools for developing plugins in Dataverse, including the Plugin Registration tool for managing plugin assemblies and steps, the Plugin Trace Viewer for debugging, the FetchXml Builder for creating and testing queries, the FetchXml Tester for executing queries, and the Early Bound Generator for simplifying entity development.

Track changes in Dataverse Owner Teams

This post discusses tracking and triggering actions in Power Automate when members are added or removed from an Owner team in a Dataverse application. It outlines setting up a Power Automate to accept HTTP calls, creating webhooks, and specifying actions for adding and removing users from the team.

Compare two arrays with Power Automate

The process involves comparing two arrays to find common or unique values. First, ensure both arrays have the same data type. To identify members unique to the SharePoint array, iterate through and compare values with the CRM array. This approach works both ways and can also discern common values between arrays by adding members based on the condition.

Track changes in Dataverse Access Teams

This post explains how to track and respond to changes in Access team memberships using Power Automate. You'll set up a Power Automate to accept an HTTP call, create a new webhook in the plugin registration tool, and configure actions for when members are added or removed. Testing the setup confirms its functionality.

Use Pipelines in PowerApps

In this example, three environments - development, test, and production - are set up and managed to create and maintain Power Platform Pipelines. After installing the Pipelines, different environments are defined and a pipeline is created with stages for testing and production. The pipelines are then utilized to deploy solutions to the respective environments, following specific steps for validation and deployment.

Condition VS Switch

A switch block allows for multiple execution paths based on a specific variable. It consists of the variable to check, cases for different actions, and a default case. Conditions check for true or false, equality, inequality, and other comparisons. Use a switch for multiple variable values, and conditions for true/false or multiple variable checks.

Maak een blog op WordPress.com.

Omhoog ↑