Conditional Unique Auto Number Sequences in Microsoft Dynamics 365 / CRM

Conditional unique auto number series

A common request for Auto Numbers in Microsoft Dynamics 365 (CDS/CRM) is to have one number field with different formats and unique sequences based on data on the record or it’s parents.
I call this “Conditional Unique Auto Number Sequences”.

Continue reading “Conditional Unique Auto Number Sequences in Microsoft Dynamics 365 / CRM”

Create view: Active Contacts in My State

Microsoft Dynamics 365 Customer Engagement and Common Data Service offer us the querying language FetchXML to retrieve data. Since this is the language used for views saved in the system, we can use FetchXML Builder for XrmToolBox to alter the features of views beyond what is possible using platform features, without making them unsupported.

Continue reading “Create view: Active Contacts in My State”

Balancing Cool Tech, Usability and TCO

I’m a techie.
I like new, shiny,
cool stuff.

Newest however, usually
costs.
And customers usually like cheap.

Users don’t care about either.
They just want a system that
empowers more than it obstructs.

So how do you find the balance between the three? Is it even possible? Or is it just another
Project Management Triangle?

Continue reading “Balancing Cool Tech, Usability and TCO”

No more Export as Unmanaged

Ever since “CRM 2011” Microsoft has been pushing the message that we should have unmanaged solutions only in Development environments. That message is being emphasized even more as we walk into the new Power Platform era.
Ideas have been raised that one day we might not be allowed to import unmanaged solutions to an environment that is not explicitly tagged for Development.

I would suggest completely removing the possibility to export solutions as unmanaged.

Continue reading “No more Export as Unmanaged”