Dynamics 365 FastTrack Architecture Insights: HR Infrastructure Merge

Hello Everyone, 

Introduction:

In this blog post, we will explore the key insights from the Dynamics 365 FastTrack Architecture Insights- HR Infrastructure Merge. The Fasttrack video provides valuable information about the FastTrack program, frequently asked questions (FAQs), timelines, and migration guidelines related to merging HR infrastructures using Dynamics 365. Let's dive in and gain a better understanding of this informative video.

FastTrack Program Overview:
The FastTrack program offered by Dynamics 365 is designed to help organizations accelerate their adoption and successful implementation of Microsoft solutions, including Dynamics 365. By leveraging FastTrack, businesses can receive guidance, best practices, resources, and direct assistance from Microsoft experts throughout their implementation journey.

HR Infrastructure Merge:

1. FAQs
   In the first chapter of the video, the FastTrack team addresses frequently asked questions related to HR infrastructure merging with Dynamics 365. They provide insights into common concerns, challenges, and potential solutions organizations might face during the process.
2. Timelines
   The second chapter focuses on the timelines involved in the HR infrastructure merge. The FastTrack team provides an overview of the different stages, from planning and preparation to data migration and go-live. They emphasize the importance of aligning these timelines with business goals and ensuring a smooth transition.
3. 
4. Migration Guidelines
   In the final chapter, the FastTrack team shares valuable migration guidelines related to HR infrastructure merging. They discuss best practices, recommended tools, data mapping considerations, and important factors to keep in mind during the migration process. These guidelines aim to ensure data integrity and a successful implementation of Dynamics 365 for HR.
5. Current state for Standalone HR & F&O environments
6. Future state for HR + F&O Environments

Conclusion:
The Dynamics 365 FastTrack Architecture Insights video on "HR Infrastructure Merge" provides organizations with critical insights into successfully merging HR infrastructures using Dynamics 365. By leveraging the FastTrack program, businesses can streamline the transition, address common challenges, and ensure a smooth implementation process. Whether you're considering a merger or already in the process, this video offers valuable guidance to support your journey.

Please remember to watch the full VIDEO on Microsoft Learn for a comprehensive understanding of the FastTrack program, FAQs, timelines, and migration guidelines.

Thank you :)

Happy learning !

Environment administrator for D365 F&O Production instance

Hello Everyone,

While provisioning D365 finance PROD instance in LCS, service accounts are recommended instead of named user accounts because of the following reasons.

• Environment cannot be able to access if the named user account is used as admin and user is not available.
• Some scenarios where only the Admin user can access an environment are:
  • First log-on after initial deployment to any environment – Only the admin user account can access the environment
  • First log-on to an environment after database movement – Only the admin user account is enabled
  • You will have to add the generic account to the LCS project as user in order to set it as environment admin
  • The Admin user is critical in some situations in the apps, such as when system batch jobs are run. These jobs must run with administrator privileges.

But in some cases, administrators realizes later after provisioning the environment with a named user.

Can change environment admin?

Yes, definitely you can change the environment admin user, but it may require a downtime. 

Impact : Causes downtime to the target finance and operations apps environment.

Prerequisites :

• You must be a project owner in the LCS project.
• The new administrator account must be a member of the same tenant that the environment belongs to.
• Plan for the downtime with appropriate approval in your organization.
• If you are going to change domain for the environment, you need to get new ISV license file(s) that references the new domain.

Update environment administrator :

For updating the environment administrator, please go through the steps explained in below.

1. In LCS, go to your project, and open your environment details page.
2. Select Maintain > Update environment admin.
3. In the dialog box that appears, select another Project Owner or Environment Admin user from your LCS project.
4. Select Save.

Please refer Microsoft docs LINK for more information.

Thank you 😊

Happy Learning.

Add or Remove fields to be available by default while using the Excel add-ins

Hello Folks,

Data management framework (formerly known as DIXF) is a powerful architecture in D365FO which supports for all integrations. Data entities which are part of DIXF is the only way (in most of the cases) to communicate with D365FO through an external system.

Recently I come across with a requirement where we need to have more default fields than the standard fields available when opened the entity data using excel add-ins. Using the excel add-in designer you can add but it may be difficult for end users to do this always and to find the required fields to add. In this post will take you through how to add or remove fields required to make defaults fields to use in the excel-addins.

In D365fo the data can be exported to excel using the “Export to excel” option which export the data for fields available in the grid, if required export more fields data you can add more fields in the grid using the personalization and insert columns.

But when you use the “Open in excel” option which uses the data entities available for the current form which can be used to manage the CRUD operations using the excel Add-in. This is a very good tool for business users to manage the data for their day to day operations. 

Coming to the main point of the topic if say customer wanted to add more fields or remove couple of fields by default when opened in excel.

For that you have to go to visual studio, open the data entity ( if the entity is standard, create extension). Go to fields field groups àAutoReport field group. Here you can see all the fields which are already showing on the excel. Now you can add or remove or change the order of the fields you want.

Once do the build, after the successful build, refresh your browser and run the excel add-in to see the expected changes.

Here I have taken the simple example of customer group standard entity, you can see the fields are already coming in excel.

Above screen shows the existing fields information, now will do modifications as follows. Here added three new fields as shown in below and you can see the results in excel after the successful build.

When the customer group opened in excel add-in, I see the change as follows. Here we see only one new field coming up in the excel sheet even though we have added three fields.

Don’t worry, there is a reason for not coming up all the fields.  There is a field property called “Access Modifier” on the entity field, by which we can restrict it. If its public then we can see the that field and if its private you cannot see the field. Out of three fields newly added, two are private and only one is public, that’s why in the new excel there is only one new fields shown.

In case, the restricted fields you wanted to enable for excel add-in for a standard entity, then you cannot change the property directly, in such case you can duplicate the entity and can make the property change to public to show it.

I hope its helpful, will come up with another interesting topic in the next post.

Thank you 😊

 

 

D365 FO Connector error : Could not retrieve values, Badgateway

Hello Everyone,

Recently come across with an issue with D365FO connector from an cloud deployed instance which was used to consume the Odata services from azure logic app and power app

Issue:

Recently got an issue with D365FO connector from an cloud deployed instance which was used to consume the odata services from azure logic app and power app. It was all working fine and one fine day all of a sudden the power app and the logic app stopped fetching the data from FnO and giving the error as “Could not retrieve values, Badgateway More diagnostics information:  x-ms-client-request-id is 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx'.

 

Root cause:

I started troubleshooting and tried to run the web instance and instance of FO is also not running with https and its only running in private. And realized certificates would have expired and checked the same in LCS and the certificates were been expired.

Solution:

I ran the Rotate certificates/Rotate Secrets using the LCS VM options, and checked for web instance which started working and the Bad gateway issue also has been resolved.

You can refer standard Microsoft documentation for the process to Rotate Secrets for cloud deployed D365FO instance.

Thanks.

Happy Learning !