Dataverse workaround wrong Autonumber Seed during Deployment
Dataverse workaround wrong Autonumber Seed during Deployment

Dataverse workaround wrong Autonumber Seed during Deployment

Introduction
For companies that operate globally, in multiple countries or regions, it is important that the users can work with product information in their own language. For example, Switzerland has 4 official languages: German, French, Italian and Rhaeto-Romanic. The first 3 languages are commonly used in business communication.

How to get Dynamics 365 Finance and Operations table sizes ? How big is my table in F&O DB?
Rather easy question to answer in good old Ax - from MS SQL Server Management Studio > right click on DB > Reports > Standard Reports > Disk Usage by Top Tables.


When utilizing the default Dataverse Connector in Power BI, users may experience occasional malfunctions. As a result, some may switch to the "legacy" connector, which is not a long-term solution. This tip aims to address a common issue faced by numerous users when employing the default connector. The specific problem is as follows:

Ensuring the accuracy and relevance of demo data is crucial in any product demonstration, whether it's during an RFP process or a standalone presentation. Often, we invest significant time and effort into creating an impressive app and/or Power BI dashboard, only to overlook the most critical aspect: the data itself. While we may have some experience in the client's industry, it's not always enough to create data that's truly representative of their unique situation.

The User Name in D365 CRM is different from that in Office 365
Table of Contents
Today, I'd like to show a note about the User Name sync mechanism from AAD(Azure Active Directory ) to Dynamics 365 CRM.

Quick overview of Dataverse Field Level Security:
Field level security in Dynamics 365 allows administrators to control access to specific fields within an entity. This means that certain users or teams can be restricted from viewing or editing certain fields, even if they have access to the overall entity.
It is also possible to use Field Level Security Profiles to group fields together, this way you can assign a security profile to multiple users or teams at once.

Are you working with CRM on-premises and developing a standalone web resources without CRM form ? You can face with this trouble and this article is for you.

Are you migrating CRM on-premises to version 9.1? Are you facing the issue and looking for a workaround? This article is for you.

Microsoft.PowerPlatform.Dataverse.Client : IFD + ADFS Mode not supported !
Valid only at the time of writing this article on 20.11.2022
