"glide.ui.list.allow_extended_fields" Pros and Cons?

[Kannan Nadar]

Hi All,

I would like to know why "glide.ui.list.allow_extended_fields" this property is disabled by default? Will there be any performance impact if we enable this?

Thanks,
Kannan

[Ct111]

in simple terms

if that is enabled then by sitting on parent table you can access child table field.

there may be not be performance issue as such but some of the functionalities won't give you result as you expect in some cases like in reports

https://hi.service-now.com/kb_view.do?sysparm_article=KB0656063

As there are very less use cases where this property is widely used hence I think it is kept as false.

Mark my ANSWER as CORRECT n also HELPFUL if it helps.

[Ajay_Chavan]

determines whether fields on extended tables can be added to a parent table list. For example, when this feature is enabled, you can view and filter on the Caller field, from the Incident table, on a Task table list.

Before you begin

Role required: admin

Note: Enabling this property does not show the extended table fields in the personalize list.

Procedure

1. Navigate to System Properties > UI Properties.
2. Locate the property Allow base table lists (task, cmdb_ci, etc.) to include extended table fields (incident_state, os_version, etc.), and allow filtering on extended table fields (glide.ui.list.allow_extended_fields).
3. Select the check box to enable extended fields on parent table lists. Clear the check box to disable the feature.
4. Click Save.

If this resolves your query, please mark my comments as correct  and helpful  .

Regards,

Ajay Chavan

My Community Articles

LinkedIn