Question
Capgemini
IN
Last activity: 11 Nov 2025 10:38 EST
Data type editor not showing dropdown/autocomplete control when sourced from data page
Hi team,
I have a requirement to show autocomplete/dropdown control in data type editor.
Property defined as source values from data page but control is not showing up when adding record in data type.
Control defined on property: pxautocomplete, pxdropdown
Control defined on datatableeditor report: autocomplete , dropdown.
Using locallist dropdowns are coming on add record.
Same configuration working fine when used in sections
Pegasystems Inc.
US
Hello,
It looks like you’re trying to update the functionality of the Out-of-the-Box (OOTB) Pega Dev Studio Data Table Editor. The issue you’re encountering is due to the Editor using a simplified grid for adding records, which doesn’t fully support advanced controls like pxAutoComplete or pxDropDown when the source is a data page. This explains why the configuration works in a section but not in the Editor.
Options to work around this:
-
Use a Section for Record Entry Instead of relying on the Editor, create a custom section that references the advanced controls. This approach ensures autocomplete/dropdown functionality works as expected.
-
Local List as a Workaround If you must use the Editor, local lists are supported (as you mentioned). For dynamic values, you’ll need to maintain the local list as changes occur.
-
Customizing the Editor (Not Best Practice) Technically, you can override the
pzDataTableEditorsection or related rules to achieve your goal. However, this is not recommended because the Editor is an internal OOTB feature, and customizing these rules can cause instability or upgrade issues.
Hello,
It looks like you’re trying to update the functionality of the Out-of-the-Box (OOTB) Pega Dev Studio Data Table Editor. The issue you’re encountering is due to the Editor using a simplified grid for adding records, which doesn’t fully support advanced controls like pxAutoComplete or pxDropDown when the source is a data page. This explains why the configuration works in a section but not in the Editor.
Options to work around this:
-
Use a Section for Record Entry Instead of relying on the Editor, create a custom section that references the advanced controls. This approach ensures autocomplete/dropdown functionality works as expected.
-
Local List as a Workaround If you must use the Editor, local lists are supported (as you mentioned). For dynamic values, you’ll need to maintain the local list as changes occur.
-
Customizing the Editor (Not Best Practice) Technically, you can override the
pzDataTableEditorsection or related rules to achieve your goal. However, this is not recommended because the Editor is an internal OOTB feature, and customizing these rules can cause instability or upgrade issues.
Unfortunately, there’s no “convenient” way to make the default Editor honor data page–based controls. Using a custom section is the most maintainable approach.
Hope this helps—let me know if you need more details!
- Nick