Different Tier in D365

Difference between Tier 1 and Tier 2 environment Dynamics 365 FO

Tier-1 Environment:

Single-box environment

All components are installed on the same server. These components include the Application Object Server (AOS), the database, Dynamics 365 Commerce, and the Management Reporter.

Microsoft SQL Server is used.

The architecture differs from the architecture of the production environment to maximize the efficiency and cost of the development team.

The environment can be cloud-hosted, or it can be deployed as an environment image (VHD).

The environment isn't suitable for UAT or performance testing.

Tier-2 Environment:

Multi-box environment

Components are installed on multiple servers.

Azure SQL Database is used.

The architecture is the same as the architecture of the production environment, even though this type of environment has a different sizing and isn't enabled for disaster recovery.

The environment can be deployed only as a standard environment or an add-on environment. It can't be cloud-hosted.

The environment is suitable for UAT and performance testing.

Microsoft Reference:

Environment planning

Change tracking in Data Entities - DMF in Dynamics 365 FO

Change tracking in Dynamics 365 Finance & Operations (F&O) is a feature that allows you to track and synchronize data changes in specific data entities with external systems or applications. This feature is particularly useful in scenarios involving data integration or data migration. Here's a more detailed look at what change tracking entails:

Purpose: It's primarily used to ensure that external systems, such as Customer Relationship Management (CRM) systems, Business Intelligence (BI) tools, or other third-party applications, remain synchronized with Dynamics 365 F&O without the need to perform full data exports.

How It Works: When change tracking is enabled on a data entity, the system keeps track of any additions, updates, or deletions made to the records in that entity. This tracking allows external systems to only pull the changes since the last synchronization, rather than having to re-import the entire data set, saving time and resources.

Types of Tracking:

No Tracking: Change tracking is not enabled.

All: Tracks all changes made to the records of the entity.

Custom: Allows for tracking changes to specific fields within an entity.

Performance Consideration: While change tracking is a powerful feature, it's important to use it judiciously as it can have performance implications, especially when enabled on large data sets or on multiple entities.

Configuration: Change tracking is configured within the Data Management workspace. You can enable it for each data entity as per your requirements.

Usage in Data Projects: In data management projects, you can specify whether to import or export only the data that has changed since the last execution, which is particularly useful for incremental data transfers.

How to enable disable change tracking:

1. Navigate to the Data Management Workspace: The Data Management workspace is where you can manage data entities and set up the configurations for data import/export.

2. Find the Data Entities Option: Within the Data Management workspace, look for the "Data entities" option.

3. Select the Entity for Change Tracking: From the list of data entities, select the specific entity for which you want to enable change tracking.

4. Configure Change Tracking: Once you have selected a data entity, you can enable change tracking by setting the "Change tracking" option to either:

None: Change tracking is not enabled for the entity.

All: All fields in the entity are tracked for changes.

Custom: Allows for specific fields within the entity to be tracked.

Save the Configuration: After configuring the change tracking options, ensure to save the changes.

Tada!!!!

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.

Terminology used in PPAC as compared to LCS

Exploring the unified vision of Microsoft's One Dynamics One Platform with a focus on LCS and PPAC terminologies in Dynamics 365 F&O.

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.

Difference between Owner and contributor in azure role

Owner Azure role:

    1. Full access to all resources in the Azure subscription.

    2. Can manage roles and assign permissions to others.

    3. Able to manage billing and subscription details.

    4. Can delete the subscription.

    5. Can add or remove resources and services.

    6. Has the authority to delegate responsibilities.

    7. Can set policies and compliance settings.

    8. Access to all data, including the ability to export data.

Contributor Azure role:

    1. Can manage everything except access to resources.

    2. Cannot assign roles or change permissions.

    3. Does not have access to manage billing or subscription details.

    4. Cannot delete the subscription.

    5. Can add or remove resources and services within their permissions.

    6. Operates under the permissions assigned by the Owner or other administrators.

    7. Can view but not set policies and compliance settings.

    8. Access to data within the scope of their role.

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.

How to enable notifications for each and every check-in in Azure DevOps ADO

Go to Azure DevOps: ADO

Go to the project setting

Now go to notifications

Now click on the new subscription

a new pop-up will come, now click on Code(TFVC), select code is checked in 

click next

In the Deliver To select Custom email address

now in the address field, enter your email id

now in the filter criteria, field select server item

now in the operator select Under

now in value select your Repos path

TaDa !!!

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.

LCS Service request support issue is getting replaced by Power platform admin center help and support

 

Work item support issues -> submitted to Microsoft will be replaced by Power platform admin center help + Support by November 2023

Link: Power platform admin

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.

Difference between "Subscription" and "Premier" support plans in Microsoft Dynamics Lifecycle Services (LCS), support issues

In the context of Microsoft Dynamics Lifecycle Services (LCS), support issues can be managed at different levels, typically categorized under "Subscription" and "Premier" support plans. Here's a general overview of the differences:

Subscription Support:

This is the standard support that comes with your Dynamics 365 subscription.

It includes access to self-help resources, Microsoft's knowledge base, and community forums.

You can submit support tickets for technical issues.

The response times can be longer compared to Premier support.

It's suited for less critical issues that don't require immediate attention.

Premier Support:

Premier support is a higher level of support service that Microsoft offers for an additional fee.

It provides everything in the Subscription support, plus a range of additional benefits.

These benefits often include 24/7 support for critical issues, faster response times, and direct access to Microsoft's top engineers.

You might also have an assigned support account manager who understands your business and technology environment.

This plan is tailored for organizations that need immediate assistance with critical issues or who want a more proactive support experience.

Enterprises choose Premier support when they require a more dedicated and immediate support experience, especially for mission-critical operations where downtime can be very costly. Subscription support may suffice for more routine issues and for businesses with less critical reliance on immediate issue resolution.

If you've made it this far, please leave a kind word. Your encouragement fuels my desire to produce and share even more valuable content.