List View Form Data Keys not working as expected when using instance values within a module

💬 App Building
, , ,
1

Hi there!

I am currently building a module in which I have the following:

  1. List view within a list view that holds form fields
  2. Both List views have Instance Values enabled
  3. Transformers that contain validation logic for the form fields and use the instance values of the outer list view

The validation logic works as expected when testing the module itself. However, as soon as I embed the module in an app, the form data keys switch to use the module name as a prefix:

[{
    textInput1: "..."
}]

thus becomes

[{
    moduleName::textInput1: "..."
}]

This happens both when I use {{ self.id }} as the form data key as well as when I override it to any other value.

For now, I have built a custom window function that removes everything before the "::" and this way normalises the object key names. However, I also need to add this window function to both the module and each app in which the module is used, which is not ideal.

It would be great if this could be resolved – thank you!

1 Like
3

Hello @nikita_from_bunch,

Apologies for the issue. Thank you for explaining the component layers and the steps, let me to reproduce this.

Could you share a screenshot of data key that has the module name as a prefix?

4

Also, have you considered using a Stepped Container component?

It might be easier to use for accomplishing the use case, as double nesting list view components and threading down variable values from these to inner nested components is definitely one of the more tricky things to do.

Which is exactly why we built out the stepped container :sweat_smile:

5

Hi @nikita_from_bunch,

Just wanted to circle back and see if the issue is still persistent and if you were able to find a work around with components without using a module.

7

Hi @Jack_T ,
thanks for following up!

I unfortunately did not further try to solve this issue as I already built a workaround using a custom window function as explained above.

In general, I am using nested list views because I am displaying data dynamically on two levels and using a module because I want the functionality to be reusable across apps. Sure, I could put the functionality directly into the parent app, but then it wouldn't be reusable anymore.

I am not quite sure how tabbed containers would help solve this issue.

Best,
Nikita

1 Like
8

No problem!

Ok I see, apologies for the confusion with the modules, we are working on a major overhaul because their function as re-usable component blocks is so critical for developers and they have become outdated.

I was thinking tabbed containers would be for the top level to toggle between various options and inside each at the lower level you could use other components. Just a thoughts.