Saturday, 4 February 2017

Force Active - Control User Property

Many time we face the situation where we are using GetFieldValue() in script for particular field and it is giving below error:

After compiling it throws error. "Unable to get field value "Field Name". The field is inactive or does not exist"

In this case we either add ActivateField() before GetFieldValue() code or we make Field property Force Active to True.

BC property Force Active, make field active even though it is not mapped to UI. So whenever BC gets called this force active field is also get queried and many times it leads to performance issue.

To avoid above situation, if you want to make a particular field force active on particular applet then you can use Control user property or List column user property to make field force active instead of making Force active at BC level and instead of mapping field in UI.

This will reduce performance issue as that field will get queried when that particular applet will get called not every time BC will get called.

Configuration is as below:

    1)  Add a control (which you want to make force active) to applet.
    2)  Add control user property as below:

     Name: ForceActive
     Value: Y

    3)  Compile your applet.

As output you can get this field value in script only for that applet without having any performance issue.

Similar user property is there for list column as well.



No comments:

Post a Comment