{"id":24297,"date":"2020-07-31T11:51:12","date_gmt":"2020-07-31T11:51:12","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=24297"},"modified":"2022-09-02T15:45:45","modified_gmt":"2022-09-02T10:15:45","slug":"how-to-create-configurable-pcf-dataset-control-using-property-set-and-property","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/07\/how-to-create-configurable-pcf-dataset-control-using-property-set-and-property\/","title":{"rendered":"How to Create Configurable PCF Dataset control using Property-set and Property"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

In our previous blog<\/a>, we have seen how to create a PCF dataset grid control to replace the Dynamics 365 CRM OOB grid. In this blog, we will see how to create a configurable PCF Control where few parameters would be taken from the user which will be used in our control.<\/p>\n

Recently, we had a requirement where we wanted to show records in the form of cards. But then the following question raised – Which fields should be shown on the cards?<\/p>\n

As seen in our previous blog<\/a> we get all the column values present in a view but what if there are 10-15 columns in a view. If we show all the 10-15 field values then the card size may get very big and we would not be able to show many records. Similarly, there were many such scenarios where the use of existing column value would hamper the consistency or standard look and feel of the cards.<\/p>\n

So, we decided to create a configurable control where the values that the user wants will be chosen by the user.<\/p>\n

For such scenarios, the first thing that pops up in mind is to create an entity for configuration and retrieve the provided field values using retrieveMultiple(). But there is a better way to get additional column values in PCF, which is by using property-set<\/strong> to get columns that are not present on view columns.<\/p>\n

Prerequisites:<\/strong><\/p>\n