Expose custom field on the Virtual entity in Dynamics 365 HR

Expose custom field on the Virtual entity in Dynamics 365 HR

Expose custom field on the Virtual entity in Dynamics 365 HR

In this article, We will see how to expose custom field on Virtual entity. There are some scenarios where you would require to add new custom fields to track additional details in Dynamics 365 HR.

Pre-requisite

Virtual entity needs to be configured in Dynamics 365 HR.

User should have an access to Dataverse

Configure virtual entity

There is already standard documentation available from Microsoft to configure virtual entity.

Configure Dataverse virtual tables – Human Resources | Dynamics 365 | Microsoft Docs

Creating custom fields

In this case, I will create a new custom field on Goal form. This entity is not available in Dataverse and with the help of Virtual entity, I will push this entity from Dynamics 365 HR to Dataverse.

Step 1 : Go to Goals form > Details

Click on Options > Personalize this page >  + Add a field

image

Next step is to add new field called : Weightage

image 1

Click on Save. Select the newly created field and Click on Update.

image 2

It shows the field on details form.

Click on View and Save as with new name “My view”

image 3

Step 2 : Custom field setup

Go to System Administration > Links > Setup > Custom fields

image 4

Select the tables from the list, Enable the entities and Apply Changes.

image 5

It will display a message at the top.

image 6

Step 3 : Generate Goals entity

Go to System Administration > Links > Integrations > Dataverse configuration

Select the entity from the list and click on Generate/refresh button.

image 7

Wait for processing.

image 8

Once this is done then you can see notification at the top.

image 9

Step 4 : Validate custom field in Dataverse table

Go to web.powerapps.com > Select your environment > Data > Tables

image 10

New custom field is added in the entity.

Step 5 : Create some data and validate in Power Platform.

Add some data in custom field in D365 HR.

The data looks something like this in D365 HR.

image 11

I have created a small power app to test data.

image 12

In this way, We can create a custom field on virtual entity use in Power Platform.

If you like this article, feel free to share it with others who might find it helpful! If you have any questions, feel free to reach out to me.

Parag Chapre

Parag Chapre is a Microsoft MVP in the fields of Dynamics 365 Finance & Operations, Human Resources, and Power Platform, recognized for his outstanding contributions to the Microsoft Dynamics community.

With over 15 years of hands-on expertise in various Microsoft Dynamics 365 areas, Parag has designed and delivered complex, innovative solutions for customers across industries and geographies. He has also provided leadership and technical guidance to project teams, managed offshore and onshore resources, and worked closely with Microsoft Product teams. Parag is passionate about sharing his knowledge and insights through his personal website, blog posts, articles, and community events. He is a member of the Microsoft Biz Apps Community Advisory Board, a Dynamics 365 Human Resource Community star, a Dynamics 365 Community contributor, and a Dynamics 365 Community Spotlight honoree.

4 Comments

  1. […] In this article, we take a look at how to expose a custom field on Virtual Entities within Microsoft Dynamics 365 Human Resources. Because Dynamics 365 HR is a sealed product, there is little room for customization. You can, however, use custom fields to insert specific data. With the use of virtual entities, you can make an integration between Dynamics 365 HR and a Power Platform. Exposing custom fields on virtual entities within Dynamics 365 HR has some great benefits for you as a D365 HR manager. It allows you to get more insights into the platform. Continue Reading → […]

    1. Hi Marek,

      Yes, custom fields are limited to forms. If your form tab is not in editable mode then your custom field cannot be editable.

      One note: when you create custom field then make it available through custom field setup and apply changes. This is the workaround.

Leave a Reply