Form DropDown Taking more time with larger dataset

8.5P1

Hello everyone,

We are experiencing a form rendering performance issue where the page takes a significant amount of time to load.

Current behavior:
Form 1: Users enter their details and select a country.
Form 2: A location dropdown is populated based on the selected country.

We have observed that the form form2 loads quickly when the selected country has a relatively small number of locations. However, for countries with a large number of locations (for example, 13,000 or more), the form (Form2) loading time increases considerably.

To address this performance issue, are there any recommended approaches for loading data into the location dropdown more efficiently?

Thank you.

Hi @Anjan_dummeda - Are you using an allowed values rule? Forms do not do well when trying to render such a large dataset. Options to consider:

Can you add additional filters so it is a little more cascading and has fewer items in each one? Example: Country>region>state>city

Use a custom object to render the list, rather than searching. Your allowed values script then just look in memory. You can pre-load this and then expect a little quicker response.

Let us know how you are calling that field.

Hi @Anjan_dummeda ,

Set dynamic and postback to true,

This will add a load button to the drop down.

Behavior will be similar to the field with type identity or any other SailPoint objects

Thanks,

Harish

Hi Ryan,

I cannot preload the location names, since it’s based on country

So, in the workflow I’m passing in an argument by loading the data into a list, please refer the below snap.

And we don’t have an option to filter the locations

I think if you use AllowedValue property, the field will not behave well for large data sets. One option you could try is to define type attribute on Field element and reference SailPoint object. As an example you could have Custom objects that represents entries in your drop down (but this can be other SailPoint object, I know some people uses Bundle, by defining specific role type that is used in the forms). There are two options to include only subset of all objects in the dropdown:

  • filterString for simple queries
  • hidden script that allows to build more complex filters
        <Field  displayName="Role Name" helpKey="Select role to update" name="roleName" required="true" type="Custom" filterString="simple query">
            <Attributes>
                <Map>
                    <entry key="hidden">
                        <value>
                            <Script>
                                <Source><![CDATA[
import sailpoint.object.Form;
import sailpoint.object.Field;
import sailpoint.api.SailPointContext;
import sailpoint.tools.GeneralException;
import sailpoint.tools.Util;
import sailpoint.object.Filter;
import sailpoint.object.QueryOptions;
import sailpoint.object.Identity;



        Filter filter = Filter.like("name", "DL-", Filter.MatchMode.START);

        field.setFilterString(filter.toString());

        return false;
]]></Source>
                            </Script>
                        </value>
                    </entry>
                </Map>
            </Attributes>
        </Field>

Field performance will be better in this scenario when you set dynamic and postback both properties of field to True.

Please give it a try and let me know.

you don’t have to use sailpoint object as type, type can still be String

Hi Lukasz,

We can use these kinds of filters when we are loading the SailPoint objects such as Identity, Bundle… etc

But in my case, we need to load the List of values from the custom object based on the country.

EX:

test1[009]

test1[010]

test1[011]

test1[012]

test1[013]

as below:

Yes, thats clear, just if you load drop down values from the list like this I am not aware of any other optimizations apart from what already have been discussed. My idea was if you could re-model entries into separate objects.

Hello Anjaneyulu. Ryan and Lukasz both raised the right angles. I would start by separating the two costs: loading the locations and rendering them.

Your lList script loads one large Custom object holding every country just to read one country’s list, and a String field with AllowedValues then renders all 13,000 entries into the form. Those are two different costs, so I would time the lookup and the render separately before changing anything.

A few options:

  • Harish’s dynamic="true": move the lookup out of the lList workflow argument and into the field’s own AllowedValuesDefinition. That defers it to field-click so Form2 opens faster, but the full list still renders once clicked, and postBack does not add paging.
  • Split the Custom object: if the object load is the slow part, per-country objects avoid deserializing every country at once. The 13k country’s object stays large though, and it does not reduce the number of choices.
  • Lukasz’s object-backed approach: the structural alternative worth testing. filterString only works when type is a SailPoint object class and filters on queryable properties, so encode the country into a queryable one such as the object name (as Lukasz filtered on name), not an attributes-map key. The Forms doc only describes these as dropdown or combo boxes and does not document paging for a workflow form, so test the actual rendering and the object-to-value mapping with a full 13k country on 8.5P1 before committing.

Since you cannot filter further, the measurement tells you which lever matters. If rendering is the bottleneck, deferring the same list only moves the delay, and if a single 13k country still struggles, a custom search-driven picker that fetches matches on demand may be the only thing that makes it fast. That aligns with Lukasz’s suggestion to reconsider the data model.