This is the second part in my series of CDS/Dynamics solution development.
In the last article, I described why you should use managed solutions and why it’s not a great idea to use unmanaged ones. I want to support my suggested best practices in this series in the future so you have the option to make your own opinion. I’m strongly for managed solutions and I’ll tell you another reason why in this part.
Have you ever heard of “missing dependencies”? Well if you are CDS developer like me, I know you have and I know that they are pain in your ***.
Continue reading “Missing Dependencies – managed vs unmanaged PART 2 (Microsoft Power Platform and CDS)”
If you are developing Model-driven app (business application) above the Microsoft Power Platform and you want to follow the best practices, you should deliver your complete solutions (zip packages) as managed solutions to all downstream environments.
Your goal should be to deploy your Model-driven app through AppSource. To achieve that, your app should be separated in smaller packages that can work on their own. For better understanding let’s say, that your app is separated in three main groups.
Continue reading “Merging Forms and Views – managed vs unmanaged (Microsoft Power Platform and CDS)”
With v9 a lot of changed. One of the major changes is client
web API, some of calls were made deprecated and some were added. For example,
The new ‘Xrm.WebApi.retrieveRecord(entityLogicalName, id,
options).then(successCallback, errorCallback)’ can’t be made synchronous. But
imagine situation, in which you need to go through multiple entities (lookups).
In this scenario, you need the result of retrieved record to access the next
record. So how can this be done?
Continue reading “Making Xrm.WebApi.retrieveRecord Synchronous calls in Common Data Service (D365 fo CE)”
There’s no breakthrough in this blogpost… It’s just to show you how does the new .csproj look like, what basic things can be done in msbuild and how-to setup ILRepack for common data service painlessly.
Continue reading “Merging DLLs in the new csproj project format (excluding specific NuGet packages)”
Hello there, fellow power platform customizers/developers! Have you tried to override the default open behavior in subgrid and failed?
What I’ve found in my research:
Documentation by Microsoft says: “You can now create a command definition for an entity with Mscrm.OpenRecordItem as the value of the Id attribute (<CommandDefinition> (RibbonDiffXml)), and define custom action for the command <Actions> (RibbonDiffXml). Customer Engagement will look for this command Id for an entity when you try to open a record from the entity-bound grid, and if present, will execute the custom action instead of opening the entity record (default behavior).”
IMPORTANT NOTE: This feature is supported only for Unified Interface.
Did this. No luck. What now? Google…
Continue reading “Override the default open behavior of data rows in an entity-bound grid”
Služba Azure Logic Apps zjednodušuje vytváření automatizovaných škálovatelných workflows (pracovních postupů), které integrují aplikace a data napříč cloudovými službami a on-premise systémy. K vytvoření vašeho řešení si vyberete z neustále rostoucí škály konektorů (momentálně asi 200) jako jsou SQL Database, Azure Services, Office 365, Salesforce, Google, Twitter a další. Tyto konektory mají různé spouštěče a akce, díky kterým Logic App bezpečně přistupuje k datům a zpracovává je.
Continue reading “Představení Azure Logic Apps”