Open detail view when selecting a value in attendance form

AppSheet AppSheet Q&A
, ,
1

Hello everyone,

I’m working on an AppSheet application and need help implementing a specific functionality that I haven’t been able to fully resolve. I would greatly appreciate your assistance.

Context:

  • I have a form called EventosAsistencia that is used to register attendance for affiliates.
  • In this form, there is a field named AfiliadoRegistro where the affiliate is selected.
  • I also have a view called VISTADetalleAfiliado that displays detailed information about the affiliates, and it is based on the Afiliado table.

Desired Functionality:

I want the app to automatically open the VISTADetalleAfiliado view to display the information of the selected affiliate every time a value is selected in the AfiliadoRegistro field within the EventosAsistencia form. This should occur before the form is saved.

What I’ve Tried:

  • I created an action to open the view, but I’m not sure how to integrate it so that it triggers when an affiliate is selected in the form.
  • I also tried setting up a Bot to trigger this action, but I encountered some difficulties with the execution conditions and the overall flow.

What I Need:

I need guidance on how to properly configure this functionality in AppSheet:

  • How can I make the VISTADetalleAfiliado view open automatically when an affiliate is selected in the EventosAsistencia form?
  • Is it recommended to use a Bot for this task, or should I use another approach?

Any specific examples, details on setting up Bots, or suggestions on the best way to implement this would be greatly appreciated.

Thank you in advance for your help.

1 Like
2

I had similar doubts a few weeks ago. The solution was to roll up my sleeves and learn Actions and Bots. After a lot of struggle, I managed to do it. Good luck.

3

You cannot navigate to the VISTADetalleAfiliado from the EventosAsistencia without saving the form. AppSheet needs a trigger, like saving the form or the click of an action button, to be able to execute your desired actions. Depending on your needs, there might be few workarounds:

  1. You can set your forms to automatically save once all required fields have values. Upon save you can set the form to navigate to the VISTADetalleAfiliado view for the selected “affiliate”. This will only make it seem as if the form is being saved
  2. If you just need to be able to see details about the “affiliate” within the form, you can use virtual columns to get reference columns from one table to display in the form in the other.
  3. Rather than using a form, select the affillitate from a table view and set up actions to add them to the EventosAsistencia table and navigate to the VISTADetalleAfiliado view

I guess my question for you is, why do you need to navigate to the VISTADetalleAfiliado before saving?

4

Thanks for the options!

Im implementing an event assistance app. A problem my organization sees, is that a lot of people who are in a certain status (ACTIVE, UNNACTIVE) are atending to meetings they are not suposed to, and a control measure is implementing opening this VISTADetalleAfiliado view, so people in charge of the gates can prevent them for entering after checking their status.

Thats why I needed to open that view before saving and registering in the form.

If there is another solution or way to achive this goal, i would be very grateful for the help

1 Like
5

It seems like option 2 would work, and perhaps with an added valid_if condition to prevent undesired people from being added. For this, it would be something like:

  1. Create a virtual column to lookup the status of the selected affiliate. The expression will depending on how your data is structured:
    1. Either a reference [Affiliate Reference column].[status]
    2. Or a lookup LOOKUP(value, dataset, column, return-column)
  2. Addthe virtual column as part of your form
    1. You could also add format rules to have the status appear green or red depending on the status for an easier visual key to the people in charge of the gate
  3. Add a valid_if constraint to the affiliate column using your ned virtual column
    1. [Virtual Status Column]=“ACTIVE”
    2. You could also add a custom explanation here for the people in charge of the gate

If you data is more complex, where people are ACTIVE for some events and INACTIVE for others, you will need to adjust accordingly. I hope that makes sense!

1 Like