What is microsoft dynamics crm / dynamics 365 CE ?
Dynamics CRM / Dynamics 365 CE (Summary)
Microsoft’s CRM platform, now called Dynamics 365 Customer Engagement (CE)
Manages sales, customer service, marketing, and field service
Built on Power Platform and Dataverse
Key apps: Sales, Customer Service, Field Service, Marketing, Project Operations
Features: customization, workflows (Power Automate), analytics (Power BI), Microsoft 365 integration
Benefits: centralized customer data, streamlined processes, strong integration, cloud-based and scalable
What is Common Data Service (CDS) / Dataverse
Microsoft’s cloud data platform for storing and managing business data
Previously called Common Data Service (CDS); now named Dataverse
Purpose
Provides a secure, scalable database for apps
Standardizes data across Dynamics 365, Power Apps, Power Automate, and Power BI
Key Features
Tables (entities) for structured data
Standard schema (Accounts, Contacts, Activities, etc.)
Business logic (rules, workflows, plugins)
Role-based security and field-level protection
Integration-friendly with Microsoft and external systems
Benefits
Centralized, consistent data
Easy app building with Power Apps
Low-code customization
Works seamlessly with Dynamics 365 CE
Explain Entities, Records, Attributes & Relationships
Entity
A table in Dataverse
Stores a specific type of business data (e.g., Account, Contact, Case)
Record
A row in an entity
Represents one instance of data (e.g., one customer, one ticket)
Attribute
A column/field in an entity
Holds a specific piece of data about a record (e.g., Name, Email, Created On)
Relationships
Connections between entities
Types:
1-to-Many (1:N) – one record relates to many (e.g., Account → Contacts)
Many-to-1 (N:1) – many records link to one
Many-to-Many (N:N) – records in one entity relate to many in another
What are alternate keys?
Alternate Keys str
unique identifiers for records, aside from the default primary key (usually the GUID or ID)
Can be used on one or more attributes (fields) to enforce uniqueness across records
When to Use Them?
When you need to enforce uniqueness for attributes other than the default GUID
To allow lookup by a field (e.g., email address, customer code) instead of GUID
For integrating with external systems where a different unique identifier is used
To prevent duplicate records based on certain fields
Example Use Case
Enforce uniqueness of an Email Address or Product Code across records, ensuring no two records share the same value in these fields.
Difference between Calculated Columns and Rollup Columns
Calculated Columns:
Compute values within the same record.
Example: TotalPrice = Quantity × UnitPrice.
Update automatically when source fields change.
Rollup Columns:
Compute values from related records.
Example: TotalOpportunities = sum of Amount from all customer’s opportunities.
Recalculate at a defined interval.
Key: Calculated = same record | Rollup = related records.
Personal Presentation
My name is J, I am 32 years old, and I am a software developer with over 7 years of experience, specializing in Microsoft technologies and enterprise solutions.
I began my professional career as a .NET web developer, where I worked mainly with ASP.NET, .NET MVC, and .NET Core, developing robust and scalable web applications. On the backend, I used C# along with SQL Server for database design and consumption, while on the frontend I worked with HTML, CSS, and JavaScript, building functional and user-oriented interfaces. This stage was key to strengthening my foundations in web development, application architecture, and programming best practices.
After approximately two years, I received an opportunity to join as a Dynamics developer, a role I have held for the past five years. During this time, I have worked extensively with Microsoft Dynamics 365, focusing on customizing and extending the platform according to business needs.
My experience includes the development of custom entities, forms, views, Business Rules, Business Process Flows (BPFs), and Web Resources using JavaScript on the frontend. On the backend, I have developed plugins in C#, applying best practices for performance optimization and event handling within the Dynamics lifecycle.
In addition, I have worked with Power Automate, creating cloud flows for business process automation, as well as classic workflows when required by the scenario. I also have experience integrating Dynamics with other systems through Azure Functions, REST APIs, and web applications developed in .NET Framework, enabling efficient communication between platforms.
Throughout my career, I have participated in projects involving system integration, process improvement, automation, and the development of custom solutions, always with a focus on quality, scalability, and delivering business value. I consider myself a proactive professional, strongly oriented toward problem-solving, and able to adapt quickly to new technological challenges.
I am currently seeking to continue growing professionally by deepening my knowledge of the Power Platform and Azure ecosystem, and by contributing my experience to projects that require solid, well-designed solutions aligned with business objectives.
