I have a messaging system…
A user contains a list of Threads which contain a list of Messages.
I have yet to work with a nested list before without structuring the back end in a weird way where I add the Parent Object unique ID to the Child object and then search for it each time with multiple API calls as the app pages change from one to another (User, Threads, Messages dynamic lists). This leads to bad UX and multiple calls which slow down the app though.
Is there a way in Dropsource to use a Detail page and pass the List Object from the initial API call instead of having to do a call on each page that gets loaded and format the back end in a way that links everything together by the Parent object Unique ID?