With the recent release of Dynamics 365 v9, you can now upload RESX files that contain localized strings. These files are used by the Xrm.Utility.getResourceString() function to provide localized strings on forms through custom scripts. But, how can you leverage the resource files on a custom web resource? One way to solve this is to use a custom action with a plugin.
With the recent release of Dynamics 365 V9, it is now possible to have Virtual Entities. These are entities that are not stored in the CRM database, but rather get their data from an OData API. This allows you to, for example, use on-premises data in Dynamics 365 without having to directly integrate it. Read on to learn how to configure this!
Azure-aware plugins can be used to run custom business logic on-premises and have the responses returned to Dynamics 365. This allows you to access internal integrate Dynamics 365 with your internal line-of-business applications.
Microsoft will begin limiting API requests on March 18, 2018.
With managed solutions, you create the initial solution and then you can create patches to that solution as you make incremental enhancements. However, you can get into a scenario where the changes in your deployed patch do not actually take effect. Consider the following scenario.