FIXED: 2025.32820: String Menu Bind issues

Bugs
1

I’ve got an example here where the page string menu parameter on the parameter DAT is used as the source for a custom parameter that is also a string menu.

Issue 1: The string menu in the parameter DAT when you hit the dropdown and choose a page will show as “Page 1” for example with quotes whereas when you do it on the custom parameter above it will show as Page 1 and then break the parameter DAT.

Issue 2: if I change the COMP on the parameter DAT this will update the string menu’s menuNames and menuLabels list but the custom parameter that is using it as a source will not update it’s own list.

Issue 3: If there is no page scoped the DAT turns into a textDAT output just saying “page” rather than an empty tableDAT with the header “page” in this example. This only happens if you only output a single column. If you output more than one column it works correctly.

Thanks!

base_string_menu_bind.tox (646 Bytes)

2

Thanks, we’re having a look.
[EDIT] We can reproduce all 3 issues now.

3

So for Issue 1:
There are actually some hidden menu behavior options (toggle vs replace) that are not exposed in 2025. We’re working on this for upcoming releases, but for now, I’ve added quotes to the built-in Page names so the menus in your example behave more identically to each other.

Issue 2 and 3: WIll be fixed in 2025.32950 and later.

Thanks for the examples.

1 Like