We are a team of specialists on the Microsoft platform, based in Switzerland but welcoming authors from all over the world. All coming from different technological horizons; AI, Web Dev, Software Dev, ...
Our team is also likely to grow over time, which is also exciting. Meet the team !
We operate on the model of a newspaper, with an editorial team aiming to select and write quality content, for all levels. Ranging from the simple trick that will surely please the beginner to the Chronicle, which will often be in the format of a study or an advanced tutorial.
Also, you can submit suggestions of subjects that interest you, on which you would like more information. We will study and may include them in the editorial roadmap.
We give our best to feed this blog as often as possible, depending on the subjects. Anyway, we have planned to update the blog on a weekly base at minimum.
We have been working for 10 years in this field, on this Microsoft application and everything that orbits around. We spent time training ourselves and then training our colleagues.
It was time to try a new sharing challenge, decentralized of our simple and only competence, but rather centralized on our common knowledge, to leverage the group effect ! This is the reason why we decided to launch Dynamics Chronicles, simply to contribute.
Insights Cards give a new way to display data in a formated and universal format. Available within a click for Dynamics 365 and usable with Power Automate, those cards can help Dynamics 365 users to be more productive than ever. And you can even create your own cards!
A Virtual entity is a custom entity in dynamics 365 Customer Engagement that have fields containing data from an external datasource. For the user, the virtual entity is displayed in your app like a regular entity but contains data that is sources from an external database. This article will focus on how to configure and use these Virtual Entities.
For some projects, you will need that developers can use dynamics365 APIs but you can't create them credentials to do it. In this tutorial, we’re going to see how to generate a secret key to connect dynamics CRM APIs.
A lot of developer is using postman to test webservices. Let’s see how to connect to dynamics 365 via postman using an identification token in order to test webAPI requests.
We must have access to Azure Active Directory in order to configure the connection.