Dynamics 365 Tech Blogs
Short Answer: No.
When you use the Dataverse application user pattern, you do not need to:
Add “Dynamics CRM” API permissions to your app registration, or
Click “Grant admin consent” in Entra ID (Azure AD).
Everything is governed by the Dataverse application user + security roles, not by Entra “API permissions”.
In the Rental Smart MVP project, we often need to display filtered data in subgrids on forms like the Property form. This helps property managers quickly view owner expenses without clutter. Here's a simple JavaScript function to dynamically filter the Owner Expense History subgrid for Bills that are historical (Paid or Void), linked to the property owner, and not unit-specific. It uses setFilterXml for UCI compatibility and assumes the subgrid is set up as a related entity grid for Charges.
The two settings that matter
Format: Date only or Date and time.
Behavior: User Local, Date Only, or Time zone independent.
These decide storage, conversion, and what users see.
Introduction:
This tutorial guides you through building and deploying a Power Apps Component Framework (PCF) control from GitHub source code (already saved to a local folder like C:\PCF\RepoName) into a Dynamics 365 (Dataverse) DEV environment. We'll use an unmanaged solution for easy edits or deletion. This method uses production builds to avoid issues like the 'eval()' security flag in the Solution Checker.
Follow the below steps to Register the Service Endpoint in the Dataverse Plugin Registration Tool.
Goal
Show how to count distinct records whose tracked columns were changed by a specific user (e.g., a Power Pages account), using Audit History only.
In Dynamics 365 Finance and Operations (D365 F&O), forms are the frontline of user interaction, but poor performance can turn them into bottlenecks—slow loads, UI freezes, and database contention frustrate users and tank productivity. Based on standard Microsoft practices and real-world developer discussions, this article breaks down four key optimization tips: judicious use of select forupdate, query indexing, minimizing client-side loops, and deferring non-essential data asynchronously. These aren't optional niceties; ignore them, and your forms will drag, especially in high-volume environments. We'll explain each with examples, assuming the latest online D365 F&O—no outdated hacks here.
In Dynamics 365 Finance and Operations (D365 F&O), working with table methods and transactions is fundamental for ensuring data integrity and extending system behavior without overwriting base code. This article dives into Chain of Command (CoC) extensions, the Transaction Tracking System (TTS), key table methods like insert/update/delete and their variants, and the nuances between validation methods such as validateField and reactive ones like modifiedField. Based on real-world discussions and standard Microsoft practices, we'll cover the essentials with examples. Assume the latest online D365 F&O version unless specified otherwise— no outdated workarounds here.
If your goal is to be job-ready as a Dynamics 365 F&O developer, here’s the list of areas that hiring managers expect you to cover. I’ve grouped them by skill area, and flagged the minimum core vs advanced/bonus:
Audience: CE developers moving into F&O or working across both.
Goal: map concepts, components, and patterns one-to-one with concise examples.
This guide walks a junior developer from a blank Azure subscription to a running integration that accepts a message, runs a Durable Function, and creates a contact in Clio via OAuth. It includes the Azure setup, the required environment variables, the project structure, and the end-to-end flow.
Source: https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-isolated-create-first-csharp?pivots=code-editor-visualstudio
Why this matters
When you off‑load sign‑in to Azure AD B2C, the portal’s native login screen is bypassed. That can make it look as if the Authentication/Registration/TermsAgreementEnabled switch no longer works. It does—there are just a few extra pieces you need to wire up.
Both localStorage and cookies let you remember things in the
browser. They solve overlapping problems, but each one shines in a different
scenario. Here’s a concise guide, plus a real example from an
“on-boarding” tooltip that only shows the first time you visit a page.
Need different Business-Process-Flows (BPFs) for the same entity record depending on a field value? The article below shows how to switch flows dynamically whenever the Appeal Type option-set changes—without hard-coding GUIDs. Drop this into your Blogger post and publish.
Portal web-roles drive what a portal user (contact) can see and do. If you only need a straightforward set-it-and-forget-it rule—no complex branching or API calls—a classic background workflow is still the quickest tool in the box.
Scenario — You need client-side JavaScript to behave differently depending on whether the portal contact holds a particular Web role (e.g. “My Demographics Access”). Power Pages doesn’t expose Web-role data directly to JavaScript, so you must pass that information from Liquid into the page.
Problem statement ↴
Records previously flagged as Ineligible (statecode = Inactive)
are later re-activated by users. Their associated Business Process Flow
rows remain inactive and stuck on an early stage.
Objective — Automatically reopen a record’s Business Process Flow (BPF) and set it to a specific stage as soon as a flag on the parent record changes, using only a background workflow (no code, no ribbon commands).
Reference: 1
There are multiple ways that you can work with related table records on a table form within Power Apps. For example, you can include related tables in read-only mode with a quick view form and create or edit a record using a main form in a dialog.
Another way you can work with related table records is by adding a form component control to another table's main form. The form component control lets users edit information of a related table record directly from another table’s form.