[NextGen UX] Text Box widget issue

Apliqo UX
1

Hi All,

I’m using Full MDX to dynamically switch data source cubes in the UI, but the UX Text Box widget isn’t saving my input properly.
Current Version: 2026.02

The image below shows the data source setting for my widget.

image
image2814×998 287 KB

When I input ‘ABC’ and click SAVE, it correctly writes back to my cube: flow_AP_notification_setup

image
image1556×648 29.2 KB

image
image820×628 47.7 KB

But when I switch to cube: flow_Cashflow_notification_setup, and do the same thing, it can not write back to the cube

image
image1508×604 29.3 KB

image
image906×716 48.3 KB

I checked the Network tab in DevTools and found that the tm1.UpdateCells request returns an error when I click Save.

image
image2720×974 255 KB

I’ve attached a screenshot showing a successful save for comparison. In this case, the tm1.UpdateCells request completes without any errors.

image
image2746×970 264 KB

Has anyone encountered a similar issue when using Full MDX for data sources? I’d appreciate any help to resolve this error. thanks!

2

What is the MDX in the dev tool? Do you see an error in the MDX that is sent to TM1?

3

MDX has no error, it correctly switched to the Cube: flow_Cashflow_notification_setup

image
image1368×374 95.1 KB

Just to add, this is the error when I click Save.

image
image1296×280 32.2 KB

4

It may be a long shot, but on your first screenshot, you have the dimension “flow_iteration_AP” as a global filter, which is dynamic on the MDX query, when you switch to the Cashflow one, potentially in some of the requests, it may be still using the “AP” one?

The error you have in the UpdateCells request is about wrong dimensions, so maybe is something like this.. you may be able to see in the “payload” what is trying to send.

You can try removing the one from the filters to see if it helps.

5

Thanks for the suggestion. I’ve tried the method you mentioned, but unfortunately, the issue persists.
I’m wondering if this is a known limitation of the current version or potentially a bug? Or is there any workaround for this issue

6

You should be able to switch datasource dynamically via a filter change trigger, so this could very well be a bug. There have been a few recent fixes to MDX updates to setting service variables. My optimistic assumption would be that this should be fixed in the 2026.04 release. If it is possible to reproduce the behaviour you describe using a standard samples model then we could create a test case and know for sure.