Many requests when use widgetOptions in a comboBox

Hello, everyone

I'm having a problem with very poor performance when using ComboBoxes that are bound to lookup fields. My list has 3 Lookup-Fields. The Workflow is, Lookup-1 select and Lookup-2 and Lookup-3 used the filter from Lookup-1.
I have the Lookups styled with .widgetOptions

var tTemplate = '#: data.LookupValue #';
var bTemplate = '#: data.LookupValue # - #: data.Title #';
//
fd.field('Pruefung').widgetOptions = {template: tTemplate, height: 400};
fd.field('Teilbereich').widgetOptions = {template: tTemplate, height: 400};
fd.field('Betriebsmittel').widgetOptions = {template: bTemplate, height: 800};

with activate .widgetOptions i have many requests on the Data.
This sample is a screenshot from open the list and click on "new" to create a new dataset. 160 request without open any combobox.

When i deactivate the .widgetOptions in the code, then only have i 69 request.

My problem is that when I enter data quickly multiple times, after opening the form 10–15 times, I occasionally see a “Throttle” message, and then I've had 3,700 requests.

That's why I looked into what might be causing the problem and came across the .widgetOptions, which generate so many more requests than they would otherwise.
Does anyone have any ideas on how I can go about this better?

Hello @Pro2000MD,

How many items are in the source list? Are you filtering options using custom code or did you configure filtering directly in the field settings?

Please also share the code you are using or an export of the form. If you prefer not to share it publicly, please email us at support@plumsail.com.

Hi Margo,

The lookup-1 has approximately 100 entrys, the lookup-2 169 entrys and the last lookup has 3400 entrys. If the filter is set from lookup-1 to lookup-3, the result set contains approximately 300–400 entries.

fd.spRendered(function () {
//
fd.field('Title').hidden = true;
fd.field('_GeltungsbereichId').hidden = true;
fd.field('Teilbereich').disabled = true;
//
var tTemplate = '#: data.LookupValue #';
var bTemplate = '#: data.LookupValue # - #: data.Title #';
//
fd.field('Pruefung').widgetOptions = {template: tTemplate, height: 400};
fd.field('Teilbereich').widgetOptions = {template: tTemplate, height: 400};
fd.field('Betriebsmittel').widgetOptions = {template: bTemplate, height: 800};
//
fd.field('Pruefung').$on('change', function(value) {

    if (!value || !value.Teilbereich) {
        return;
    }
    //
    // Set Value from the Field "Teilbereich"
    fd.field('Teilbereich').value = value.Teilbereich.Id;
    fd.field('Teilbereich').refresh();
    
    // Set Value from the Field "_GeltungsbereichId"
    fd.field('_GeltungsbereichId').value = value.OData__GeltungsbereichId;
});

});

The filter is setting over the designer.

Hello @Pro2000MD,

Thank you for sharing this. I don't see where the problem comes from. Could you please record the network logs and send them along with the form export to support@plumsail.com?