<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:blog="http://dnn-connect.org/blog/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Blog - #ModelDrivenApps</title>
    <link>https://www.xrmlabs.com/About-Us/XRMs-Blog/term/3040/locale/en-US/Blog-ModelDrivenApps</link>
    <description />
    <managingEditor>sales@xrmlabs.com</managingEditor>
    <pubDate>Tue, 28 Apr 2026 00:17:12 GMT</pubDate>
    <lastBuildDate>Tue, 28 Apr 2026 00:17:12 GMT</lastBuildDate>
    <category>#ModelDrivenApps</category>
    <generator>DotNetNuke Blog RSS Generator Version 6.5.2.0</generator>
    <ttl>30</ttl>
    <atom:link href="https://www.xrmlabs.com/DesktopModules/Blog/API/RSS/Get?moduleid=440&amp;tabid=94&amp;term=3040" rel="self" type="application/rss+xml" />
    <item>
      <title>Customizing Out-of-the-Box Buttons</title>
      <link>https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8675/Customizing-Out-of-the-Box-Buttons</link>
      <description>&lt;p&gt;In Microsoft Dynamics 365, the command bar (ribbon) provides users with quick access to key actions such as creating records, assigning ownership, activating or deactivating records, and more. While these out-of-the-box (OOB) buttons are helpful, business processes often demand tailored functionality. This is where the Ribbon Workbench becomes a powerful tool for extending and customizing the standard user experience.&amp;nbsp;&lt;/p&gt;
</description>
      <category>#CRMSecurityRoles</category>
      <category>#D365Customization</category>
      <category>#EnableRules</category>
      <category>#ModelDrivenApps</category>
      <category>#RibbonWorkbench</category>
      <category>#XRMLabs</category>
      <guid isPermaLink="true">https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8675/Customizing-Out-of-the-Box-Buttons</guid>
      <pubDate>Tue, 04 Nov 2025 17:48:00 GMT</pubDate>
      <media:thumbnail width="144" height="96" url="https://www.xrmlabs.com:443/DesktopModules/Blog/BlogImage.ashx?TabId=94&amp;ModuleId=440&amp;Blog=1&amp;Post=8675&amp;w=144&amp;h=96&amp;c=1&amp;key=468a136a-0d5b-466e-a93c-fcce6ecc2af7" />
      <blog:publishedon>2025-11-04 17:48:00Z</blog:publishedon>
    </item>
    <item>
      <title>Power Apps Grid control with custom filtering</title>
      <link>https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8663/Power-Apps-Grid-control-with-custom-filtering</link>
      <description>&lt;p&gt;When working with Dynamics 365 and Power Apps, one of the most common requirements is to show related records in a way that is both user-friendly and intuitive. Instead of making users click into multiple forms and tabs, you can leverage the Power Apps grid control to display related records, configure child relationships, and even apply dynamic filtering so users only see the records that matter.&lt;/p&gt;
</description>
      <category>#Dynamics365Customization</category>
      <category>#ExpandCollapse</category>
      <category>#ModelDrivenApps</category>
      <category>#PowerAppsGridControl</category>
      <category>#RelatedRecords</category>
      <category>#SubgridFiltering</category>
      <guid isPermaLink="true">https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8663/Power-Apps-Grid-control-with-custom-filtering</guid>
      <pubDate>Thu, 18 Sep 2025 09:34:00 GMT</pubDate>
      <media:thumbnail width="144" height="96" url="https://www.xrmlabs.com:443/DesktopModules/Blog/BlogImage.ashx?TabId=94&amp;ModuleId=440&amp;Blog=1&amp;Post=8663&amp;w=144&amp;h=96&amp;c=1&amp;key=7f17944a-3359-43c9-bf80-efdc3aa434f6" />
      <blog:publishedon>2025-09-18 09:34:00Z</blog:publishedon>
    </item>
    <item>
      <title>Environment Variables in Dynamics CRM</title>
      <link>https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8635/Environment-Variables-in-Dynamics-CRM</link>
      <description>&lt;p&gt;Environment variables in Dynamics 365 (Dataverse) are special solution components that serve as environment-specific configuration settings. They allow you to store a key (unique name) and a value (such as text, number, JSON, secret key, etc.) outside your app or flow, so it&amp;#39;s easier to manage.&amp;nbsp;&lt;/p&gt;
</description>
      <category>#Dynamics365</category>
      <category>#Dynamics365Configuration</category>
      <category>#Dynamics365EnvironmentVariables</category>
      <category>#Dynamics365Tips</category>
      <category>#DynamicsCRM</category>
      <category>#EnvironmentVariables</category>
      <category>#ModelDrivenApps</category>
      <category>#PowerAppsDev</category>
      <category>#PowerPlatform</category>
      <guid isPermaLink="true">https://www.xrmlabs.com/About-Us/XRMs-Blog/Post/8635/Environment-Variables-in-Dynamics-CRM</guid>
      <pubDate>Mon, 28 Jul 2025 11:31:27 GMT</pubDate>
      <blog:publishedon>2025-07-28 11:31:27Z</blog:publishedon>
    </item>
  </channel>
</rss>