Create a child page with an add connected record form & return to parent

I can’t find any way to achieve something that should be very simple. What I want to do is go from a Details Page, to an edit page, add a form to insert a new connected record, and then return the user to the parent page.

This, and another situation where it’s impossible to create a child page, and then create a 2nd button on the same parent that links to the child, seem to be incredibly restrictive. In that instance, I literally have to recreate the entire form, and all the rules, just to move the link to a different section of the page. That doesn’t seem right.

Is this meant to be this way? Is it something that is just going to improve in terms of functionality over time? Are these sorts of restrictive page building connections the intended function?

It’s preventing me from accomplishing very basic, simple things that would be an obvious part of a user interface like the one we are building. Right now, I’m trying to figure out how to let someone add a support ticket and return to the details page, and it’s seemingly not possible.

Am I missing something here @moe @Chem @tim.young?

Hey @Tophinity

I’m not at my computer right now but I’m almost certain that there’s an option to return to parent on form submit rule -> redirect. Maybe I’m remembering it in a different context though. I think it’s meant to go from a details (child) page to a parent page.

Just to clarify, you want to go from a grandchild page back to the record details page?

So I’m not sure what the top level page is but you’re clicking a record to go to a details page where you can see tickets for the record? I know it’s hard to break from a design idea but why not use the “add new record” form option on the tickets component?

As for the second thing you mentioned about buttons, I’m not understanding what you’re trying to do, I’m sorry.

Would you mind sharing some screenshots?

Wont work from Edit form, you’ll need to stay on Details form and add sub-form for your child or grandchild records under Details of parent block.

Updates to record on Details form also possible by setting detail form property options as shown below

I hope this helps

1 Like

I’m very interested in understanding the “WHY” here. To my mind, it seems incredibly restrictive, but with no received benefit from the restrictions being imparted.

Here’s what I’m trying to do.

I have a main landing page. The owners of each business then click on “My Businesses”. Some owners own more than one business.

So, they need to then be able to select which of their businesses they wish to view. That’s a page that has a list view. From there, they click on the business to access that businesses dashboard.

The businesses dashboard is a details view that is a child of the page with the list. From that dashboard, they need to be able to do things like “Add A New Support Ticket”. In order to do this, I need to create either a details view, or an edit view as a child of the details page I am now in.

I created an “edit” view, deleted the auto-created edit form on that new child page, and added a form to insert a new connected record.

From that page with the add new connected record form, there is no way to return the user to their business details page. My only option would be to return them ALLLL the way back to the original list view, where they would again have to select the business to enter the same dashboard they were on when they decided to submit a support ticket.

In addition to that, there’s also no way for me to create a second link to the new edit view that I created (the one with the add connected record form). Even from the exact same page. I can’t create a link to that new view, literally even on the same page that the original link is on. That page/view/form is completely cut off from the rest of my application. I have only one single point of entry to the form, and no point of return.

Something is definitely not right there @tim.young.

To add to this, the child page restrictions are a pretty big disaster for my build. One of the things that kept our app clean on Knack, is that we were able to direct users to the same edit forms from many pages. This allowed us to have a reasonable number of edit forms to maintain (vs having to update 10 edit forms every time there’s a single change).

In Tadabase this appears to be impossible, meaning that the number of forms I have to create to serve the exact same purpose is going to increase five-fold (to be conservative).

I’d like to know if these are issues that Tadabase considers priorities, or whether I should go back to the team and say “I’m not sure how we build this piece in a long-term manageable fashion given these limitations”.

These aren’t just things I’m looking for a workaround for. I’m looking for some actual understanding of why it’s like this, and whether improvements will be made. I really don’t want to build 5 times more forms than we already have.

I also really don’t want to continue to use convoluted workarounds (like adding matching fields in one object so that I can then use those fields to insert a connected record via form rules into the destination object. So two times as many fields, and an extra process to run, instead of just adding a connected record directly using a form.)

That’s a complete disaster waiting to happen when we miss edits. Have forms that are supposed to be the same, but where we forgot to update rules. Trying to diagnose bug reports, and trying to determine exactly which of the many forms the user was using. Etc.

I’m happy to elaborate on this further. I’d even be willing to share my screen on a Zoom call to discuss further. Anything I can do to help better communicate this use case.

Thanks Tim (and all)

Thanks @Shumon. I can’t use the inline editing, because I’m adding new records. There is no existing element where there would be anything to edit inline, and there’s no element that would allow for an “add new record” form that would work in the context of the dashboard I am building.

I’m not sure I understand what you mean about the other part. Maybe Tim’s next answer will help clarify that piece. Thanks again.

add business ID to ticket record using record rules to new ticket submit. you’ll have dashboard ID auto inserted into ticket table if connections are one-to-many.