#2316 Issue with "Customized Request Forms" Extension – OQL Drop-down Error when Assigning Multiple Templates (iTop 2.4.3)

[Cristian Ozan]

Description:

We are experiencing an issue when using the "Customized Request Forms version 2.4.3" extension in iTop version 3.2.1.

The error occurs only when multiple templates (more than one) are assigned to a service subcategory. Specifically, the problem appears with fields of type Drop-down List based on OQL queries.

When we attempt to create a new request under these conditions (Only in portal user), we receive the following error message:

Field with ID "code_xxx" was not found in the Form of ID "cf_service_details-subform_user_data".

(See attached screenshot for reference.)

This error prevents the proper rendering and submission of the request form. The issue seems to be related to how the form dynamically handles multiple templates with OQL-based drop-down fields.

Steps to reproduce:

Assign more than one request template to a service subcategory.

Include at least one field of type "Drop-down List (OQL)" in each template.

Try to create a new request from the portal interface.

The form fails to load correctly and throws the error shown above.

We would appreciate your assistance in reviewing this issue and providing guidance or a fix if available.

Thank you in advance.

[Shorty1]

We also do have that problem.

[Vincent @ Combodo]

Until release of a fix within 3.2.1-1, you should reduce the number of proposed objects in the field drop-down under the max_combo_length value (which can be increase also)

[Cristian Ozan]

Thank you for your response.

I have already set the max_combo_length parameter to 1000, and the OQL query used in the field is a simple:

SELECT Organization

There are approximately 780 records in the Organization table, so this should be within the allowed limit.

However, the error still occurs when assigning more than one template to the service subcategory. The issue seems to persist regardless of the max_combo_length value.

Let me know if there's anything else I can try or if a workaround is available until the fix in 3.2.1-1 is released.

Thanks again.