{"id":32650,"date":"2022-09-21T17:05:29","date_gmt":"2022-09-21T11:35:29","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=32650"},"modified":"2022-10-13T14:36:04","modified_gmt":"2022-10-13T09:06:04","slug":"setting-as-a-solution-component-in-power-apps","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2022\/09\/setting-as-a-solution-component-in-power-apps\/","title":{"rendered":"\u2018Setting\u2019 as a solution component in Power Apps"},"content":{"rendered":"

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

In this blog, we have explained the Setting component of a solution and how to configure or edit the settings using the same. Earlier, this feature was not present in Power Apps, but it has been made available in the 2021 Wave 1 release. The setting component allows administrators or customizers to enable or disable any of the available features. Let us see how to set up the same.<\/p>\n

Setup<\/strong><\/h3>\n

Application administrators or customizers can create a \u2018setting\u2019 definition. <\/strong>They can include the setting defined in the same solution that is used to deliver the feature to their customers.<\/p>\n

To Setup the Setting component you need to navigate to your solution and then navigate to<\/p>\n

New-> More -> Setting -> Setting definition<\/strong><\/p>\n

\"solution<\/a><\/p>\n

This will open a side pane where the settings can be configured with all the fields that include properties such as name, description, data type, and default value as shown below.<\/p>\n

\"solution<\/a><\/p>\n

Value can be changed for:<\/strong><\/p>\n

Here, we define where to apply the \u2018setting\u2019 definition. We can either apply the setting on the Environment level or on the App level or on both. If we choose the None value then the settings shall not be applied.<\/p>\n

Setting environment value:<\/strong><\/p>\n

Now in the property \u201cValue can be changed for<\/strong>\u201d we set if the setting shall be applied on an Environment or App or both. However, it will only be applied on the Environment level if the value of this property is set to Yes<\/strong>.<\/p>\n

Setting app value:<\/strong><\/p>\n

Again, in the property \u201cValue can be changed for<\/strong>\u201d we set if the setting shall be applied on an Environment or App or both. However, it will only be applied to an App if the value of this property is set to Yes<\/strong>.<\/p>\n

Also, from the above screenshot, it can be seen that if the solution on which we are defining the setting for if contains any Model Driven App(s) then that will get listed out. Where we shall set the App value to Yes or No. And the setting will get applied only on the App(s) for which we did set it to Yes.<\/p>\n

On saving the above Setting component, a Setting Definition record gets created with the same name which can be accessed programmatically using the below fetch in both client-side as well as server-side code.<\/p>\n

<fetch><\/code> <entity name=\"settingdefinition\"><\/code> <attribute name=\"defaultvalue\" \/><\/code> <attribute name=\"overridablelevel\" \/><\/code> <attribute name=\"isoverridable\" \/><\/code> <filter><\/code> <condition attribute=\"uniquename\" operator=\"eq\" value=\"logicalname<\/strong>\" \/><\/code> <\/filter><\/code> <link-entity name=\"organizationsetting\" from=\"settingdefinitionid\" to=\"settingdefinitionid\" link-type=\"outer\" alias=\"OrgSetting\"><\/code> <attribute name=\"value\" \/><\/code> <\/link-entity><\/code> <\/entity><\/code> <\/fetch><\/code><\/pre>\n
Now let\u2019s see how to enable the features from Settings in the app designer.<\/p>\n