In this video, we discussed the app sheet actions that you can use in your app to navigate the app user two different views in the current app or to another app. Let's review the app navigation actions that are currently supported by app sheet. The action type app copy this row and edit the copy. Creates a copy of the current data row in the table that is being used in the app and opens the copy in a form view. For example, a sample inventory app displays shipment transactions. To accommodate additional shipments for the same product, you could use this action type to duplicate an existing transaction and modify the shipment quantity. To implement this functionality, we follow these steps. Create and name the action. Copy shipment. Set the table to which this action will apply. Shipping. Set the action type, app copy this row and edit the copy. Then in the appearance section, set the action icon. The display prominence, display overlay. Then, enable the needs confirmation option. And set the confirmation message from that the app user sees when the action is invoked. Now, when viewing a shipment transaction in the app, the user clicks the copy shipment action. And confirms the copy of the shipment transaction by clicking copy shipment. After confirmation, the shipment form is displayed with the column values copied from the original shipping transaction. The user then edits the shipping information and saves the form. When the app syncs with the data source, a second shipment transaction is added to the table. The action type app export this view to a CSV file, downloads the rows in the current view of a table to a CSV file. Note that the action only works for an app that requires users sign in, and is running in a desktop browser. You may want the app user to be able to download data from certain views in the app. For example, to keep a record of certain types of transactions. When configuring this action, you must pacify the locale of the CSV row data. That is exported by either selecting one of the supported locales. Or specifying an expression that evaluates to a locale identifier of one of the supported locales. For example, ENUS. More details on this action type can be found in the documentation on the app sheet website. The action type app go to another Appsheet app, opens an Appsheet app that is different from the current app. You must configure this action with the deep link to the target app. The target can contain an expression to compute the deep link at the time the action is triggered. You can use the link to add function to construct the deep link to the target app. The action type app go to another view within this app, takes the user to another view in the current app. You must configure this action with a deep link to the target view. The Target, can contain an expression that uses the link to view function to compute the deep link at the time the action is triggered. Let's create an action that navigates a user from one view to another in the app. In the example soon, we have a list of products with current inventory levels stored in a table. Let's add an action that enables the app user to create a shipping request for products that have a current inventory level above 10 units. To do this, first click add new action to create the action. Then configure the action by setting the following, action name, ship for a record of this table, choose the products table. In the do this field, select app, go to another view within this app. For the target view, we use the link to form function with shipping outbound form, which is the name of a form view that was previously created in the act. We used the expression assistant to build the deep link, using the link to form function. The link to form function constructs a deep link to the form view, with the value of the specified column pre filled in the form. In the appearance section of the action configuration, select an appropriate icon for the action. Set the prominence to display overlay, so that the action icon is displayed in the action bar in the app. Next, we set the conditions for this action to be shown in the app. We want the app user to be able to use this action only on those products with the current inventory level above 10 units. Use the expression assistant again, to set the condition using a yes no expression. After saving these changes to the app, you can now see the new ship action icon displayed only for those roles in the products table that satisfy the actions condition. Clicking on the ship icon for a specific product navigates the app user to the configured form view with the product details automatically populated. In this form view, the app user can now enter the required information to create a shipping entry for the product. The action type app in Poto CSV file for this view, uploads a rose in a CSV file to the current view. Not that this action only works when the app is running in a desktop browser. You can use the import action type to add one or more new records to an app sheet table or update one or more existing records in an app sheet table. More details on this action type can be found in the documentation on the app sheet website. The action type app open a form to add a new row to the stable. Opens a form view that enables users to add a new row to the current table. Note that this action differs from the previously discussed action app, go to another view within this app. In that this action can only be used to open a form view for the current table. You can use this type of action to customize the action icon and it's display prominence inappropriate app views, instead of using the system add action. To hide the system, add action in such scenarios, you set its display prominence to do not display in the appearance section of the action definition form. The action type app open a form to edit this row, opens a form that enables users to edit a row in the current table. The actions to open a form to add a new row or edit the current row are similar to their system action cousin add and edit. You can create these actions in addition to the system actions when you need to display them differently in the app. For example, the supplier stable in our sample inventory management app contains a detailed view of a supplier row with the default system edit action. In addition to this default edit action, we want the app user to directly edit a supplier role from the table view that displays the list of suppliers. To implement this, we create a new action with the name Edit Suppliers. Set the table to which this action applies suppliers. Set the action type app, open a form to edit this row. In the appearance section, we can figure the action icon. The prominence of the icon so that it displays in line with the row. The attached to column supply a name that the icon is attached to when displayed in line in the app. Finally, since we want to display this action only in the supplier table list view, we said only if this condition is true. Yes, no expression, using the built in context function that returns true, if the current view in the app is the supplier table view. For details on the context function, view the documentation on the app sheet website. As you can see in the live app preview, we now have the edit action displayed in line with each role in the supplier table view. By clicking the edit icon, the app user can edit the supplier row directly using the supplier form. By clicking the supplier name, the app user navigates the supplier detailed view. In this view, the app user can click the system edit action to edit the supplier using the same supplier form. Note that, there is a new beta quick edit feature in app sheet. That if enabled for a table view, allows the app user to edit column values in multiple rows together in the same view.
