Tip #854: Beware of Using Xrm Client Functions As Callbacks

Today’s tip comes from the tipper who, despite his affinity with Microsoft Flow, earned his place amongst the real developers fair and square, and who is now known as Daryl “Always Raising” LaBar. Daryl, you have the floor Writing clean code is constantly at the for-front of developers, and usually, “less” code generally results in […]

Tip #827: Restricting date picker on portal forms

Aztec calendar

This tip comes directly from none other than Tanguy “The XRM Toolbox” Touzard himself. It’s super easy to build an entity form and a page to allow editing of the Dynamics 365 records in a portal. But what if we want to restrict a date picker control to a certain range, which could be dynamic, […]

Tip #787: Creating records in Project Service

Dictionary key

When creating records for one of the Dynamics 365 solutions, you may find yourself in the same situation as Guido “Trekkie not Star Wars fan” Preite. The simplest possible code to create msdyn_actual (part of the Project Service) generates “The given key was not present in the dictionary” error. One of the advantages (and curses) […]

Tip #768: Avoid running out of memory when using CRM context

Low memory

When you process large data in your code, email attachments, for example, there is always a danger of running out of the available memory. Consider this code dealing with the email attachments: The danger here is running out of memory on retrieval of the file attached to the CRM notes. Even though from C# point […]

Tip #767: Server-to-server authentication is here

Headless

Woot, woot! At long last we can create passive clients – the ones that do not have someone sitting in front of them. Clients like web sites or services – and authenticate them without using username and password AND get the magic bearer token that is good to use in Web API. The detailed walkthrough […]

Tip #746: Bring in the specialist

Workflow auto bringing the specialist

Washing car on weekend is something that everyone can do on their own. Probably. But if some serious cleanup is required, one’s better off calling Mr Wolf. Same goes for complicated cases in customer service. If you run a secure shop that deals with the cases that include sensitive or personal identifiable information, then security […]

Tip #731: Hide and protect your custom CRM API

Protect yourself by covering

Yesterday we illustrated how you can wrap some server-side functionality as a custom API to be consumed by the developers. One of the undesired side effects is that business can now poke their nose into the API when building workflow processes: If your API is a smoking gun and you don’t want business to accidentally […]

Tip #730: Turn your CRM into API machine

Locked black box

When people ask me to describe the differences between custom workflow activities and custom actions, I always use the following definitions: Custom workflow activities. A functional blackbox created by the developers to be consumed by the business Custom activity. A functional blackbox created by the business to be consumed by the developers There is more […]