Common Data Service Archives - NETWORG

CDS Solution Development – Best Practices – Developed Components

Introduction.

Hi all! Another week went by, another page in the GitHub wiki added… In case you’re new here, read this article which explains the motivation behind it all.

There’s not a lot I can comment on for these few new pages. But I can think of one thing.

CDS Solution Development – Best Practices – Tooling

Introduction.

Hi all! Another week went by, another page in the GitHub wiki added… In case you’re new here, read this article which explains the motivation behind it all.

What are my thoughts on current CDS tooling? Let’s get into it.

Missing Dependencies – managed vs unmanaged PART 2 (Microsoft Power Platform and CDS)

Introduction.

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 ***.

Merging Forms and Views – managed vs unmanaged (Microsoft Power Platform and CDS)

Introduction.

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.

Making Xrm.WebApi.retrieveRecord Synchronous calls in Common Data Service (D365 fo CE)

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, Xrm.WebApi.

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?

Novinka Common Data Service 2.0 v souvislostech

Pokud to trochu sledujete, ale začínáte se ztrácet v posledních novinkách v oblasti informačních systému Microsoftu, tak určitě nejste sami. Microsoft totiž chodí s kladivem, rozbíjí je na menší části a se snaží poskládat moderní platformu, která obstojí v dnešním cloudovém světě, kde se vše mění dříve než se to pořádně dostane k uživatelům.

Níže si můžete přečíst o situaci v kontextu CRM a platformy Common Data Service, kterou považuji za zásadní pokrok. Přinese totiž robustní informační systémy i do menších organizací a prováže technologie, které si dodnes spolu povídaly jen draze a složitě.

Continue reading “Novinka Common Data Service 2.0 v souvislostech”

Historie Dynamics CRM / CE / 365 for Sales

Jako základ pro další články a informace o platformě považuji za nezbytné, abych přiblížil historický kontext a vývoj platformy, která dnes stojí za službou Common Data Service a jistě ji čeká další velká budoucnost, protože byla zvolena jako základ pro budoucí business aplikace Microsoftu a stejných způsobem je otevřená jako stavební základ pro nás a různé aplikace třetích stran.

Continue reading “Historie Dynamics CRM / CE / 365 for Sales”