"New"/Add in nested table

[Phil_Waite]

Hi,

I have an outlet main table with a child table for orders and another for order details.

Related or details show in the referencer view of an outlet in the main table. The nested related orders has “View” and “New” to take the user to either the related orders or to a form to create a new one.

I can create different form views with slices of the orders table and create a new Add action button that overlays. I can then choose whoch form view the user is taken too. If I se the system generated “Add” action to “Do Not Display” then “New” link disaapears - the problem is I can’t get my “add” action that I have created to show a “new” link.

thanks

Phil

[Aleksi]

Unfortunately that’s a normal behavior. You can hide this “New” button, but you can’t choose any other action for that button.

[Phil_Waite]

Hi Aleksi,

Thank you. How can I change the columns shown in the form view without just unchecking the “Show” botton on the table. I want sales users and delivery driver users to see a different combination of the columns in a form.

Thanks

Phil

[Steve]

help.appsheet.com

Slices: The Essentials

Display only certain rows or columns of your table with slices.

[Phil_Waite]

Hi

Thanks Steve, The problem I am having is an action made by me appearing in the nested related orders row in the parent table.

If the “new” button only appears for the system generated one then I could have another table that assigns each USEREMAIL() to be either a “Standard View” or “Delivery Driver View” and columns would appear in the form for placing a new order based on USEREMAIL().

Cheers

Phil

[Steve]

Unfortunately, there is effectively no way to replace the system-provided New or Add button for table views. You can hide it with Do not display and/or prevent its use altogether by setting the Only if this condition is true expression to FALSE. There is no way to add a custom action that does anything different in its place.

What I understand you want to do is provide an Add/New button that sends the user to a different view according to who the user is. I see two ways to approach this:

1. Create a single form that serves both types of users, then use the Show? (Show_If) (or Editable? (Editable_If)) property of each column to selectively show or hide (or enable or disable) columns according to the user.

   OR

2. Create an overlay button for the detail view that navigates to the appropriate view.