Context: we want to re-use components between different apps, modules are the way to go for that. These are repeatables though (e.g. different record types) and would be best suited in list views. The problem is that list views do not support modules. In addition, trying to add a module to a list view fails in an obscure and unfriendly way, with the error message "Cannot place a undefined inside a List View".
4 Likes
Hey @erispoe
we want to re-use components between different apps, modules are the way to go for that. These are repeatables though (e.g. different record types) and would be best suited in list views. The problem is that list views do not support modules.
I've added you to our internal feature request to support modules in repeatable contexts, but this isn't currently on the road map. Our team will be sure to update this post if this changes at a future point though.
For now, would you be able to create the Listview itself within the module?
In addition, trying to add a module to a list view fails in an obscure and unfriendly way, with the error message "Cannot place a undefined inside a List View".
Placing a module in a Listview should not be possible. But you can get around this if the module is in a container which leads to that Cannot place a undefined inside a List View error—this is a known issue.
Hi @everett_smith, I'm not sure what you mean by:
The goal is that modules themselves are elements of a listview.
To clarify, if you only were trying to use a single Module in a Listview without any other components, then you might be able to create the Listview within the Module itself.
If you need to use multiple Modules or a Module with other components in a Listview, then this wouldn't work.
I also need this functionality. I'm trying to create a dynamic form with nested components (i.e. a user needs to submit a project with multiple work requests and each work request has multiple tasks associated with it). Without the ability to use Modules inside of ListViews, this will become a mess of duplicated code that will be very difficult to maintain over time.
1 Like
Hi @Javi_Muhrer! Welcome to the community. 
I'll add your feedback to the internal conversation that we have going. It does sound like modules will be a focus for our team in the coming months, so I anticipate being able to share an update relatively soon!
Thanks Darren!
Is there any update on this? Excuse my strong criticism here - I love retool in other places but this seems insane. I'm not able to create my own 'avatar' module and reuse it in repeatables across my applications? 
Is there a workaround for this? Eg can I create react views that I can place in repeatables?
Hey @Lychee - I appreciate the candor and think that you managed to maintain a professional, respectful tone while still communicating clearly. 
The short story is that this has turned into a bigger lift than we first anticipated, mostly due to the fact that modules contain their own queries. This level of nesting has some unanticipated and undesired side effects.
For relatively simple use cases - like a user avatar, hopefully - you should be able to accomplish the same goal with a custom component. These are super flexible components that you can build locally in React and then deploy to Retool. Let me know if you have any questions getting started!
Awesome thank you I will try using custom components!
Hello folks,
Coming around to kindly request support for this 
In my case we are looking to use Modules within Table Expandable Rows - which are ListViews under the hood based on the error we are getting.
From the discussions I have seen around, the problem seems to be the queries that run under the hood.
Could this be solved at once with Modules v2.0 supporting lazy load? (mentioned here)
1 Like
Thanks for the bump, @Samuel_Andreo! I've passed on the feedback and look forward to giving you and the others here a satisfying update as soon as I possibly can.
1 Like