Bug Report: Custom AC Module - Grid Type Data Binding Not Evaluating Component Proxy Values in App Connect 2.2.2

Wappler Version : 7.5.2

Operating System : Linux/Windows
Server Model: NodeJS
Database Type: Postgres
Hosting Type: Docker

Expected Behavior

When using dmx-bind with grid type attributes containing component proxy property references, the component should fetch/parse proxy object values to their actual values before passing them to the component JS.

Example: A grid binding like dmx-bind:val_api_params="[{key:'processor_id',value:fi_processors.value}]" should evaluate fi_processors.value to the actual selected value (e.g., "1") instead of returning null.

Actual Behavior

In App Connect 2.2.2, when using grid type bindings with component proxy property accessors, values should get parsed, This was working fine in App Connect 2.1.5

How to reproduce

  • Custom Module That rely on using grid data type are breaking as a result of this parsing issue
{
  name: "valApiParams",
  attribute: "dmx-bind:val_api_params",
  type: "grid",
  jsonFormat: true,
  columns: [
    {
      field: "key",
      editable: { type: "text" }
    },
    {
      field: "value",
      editable: { type: "datapicker" }
    }
  ]
}

Additional Info

if i don’t use the .value, Then i get the Proxy Object, Adding the .value gives me null
dmx-bind:val_api_params="[{key:'account_id',value:fi_account_id},{key:'service_type',value:fi_account_id.value}]"

{key: 'account_id', value: Proxy(Object)}
{key: 'service_type', value: ''}

@George @patrick Could you please look into this one, Most of the AC Custom extensions are using the grid type objects and they are breaking now in 2.2.2 versions.

Any update on this??

I would need some extra info, what kind of custom component is it, how is the attribute defined?

I assume that fi_account_id is also a component on the page, probably a dmx-value component. Is that having a dynamic value that isn't directly available? I think that the empty string value that you get is the default value from the fi_account_id component from before the dynamic value was loaded and the binding on your custom component didn't update with the new value.

I need some test case where I can reproduce this. Currently I'm only guessing and can't reproduce it.

I think that I've found a way to reproduce it and have a fix, please test if it actually fixes your component also.

dmxAppConnect.zip (134.3 KB)

1 Like

Thanks @patrick . That Fixed it :hugs:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.