Hi
Here is what I'm trying to achieve and I want the most efficient way you think I can do it :
I have a table named Activities. That table refers to multiples activities in différents domain so each activity has its own set of Tasks. What I'm trying to achieve is to create a View where users can select activities in one dropdown menu and then depending on the activity they choose, appsheet will generate a form with labels of tasks only related to it.
Hope you understand my problem and thanks for the Help..
If it's a dropdown field deoending on a previous one, this is called a dependent dropdown.You can have as many levels as you want. Dependent Dropd-downs
And see the sample app here Dependent Dropd-downs sample app
Or it could be you're talking about a related table hence you need ref type columns for parent to child relationship.
But you also mentioned genetate a form, so maybe it's more about deep linking using LINKTOFORM().
It's unclear what you really want here.
Hi,
Thanks for your reply. I already have a good understanding of Dependent Dropd-downs . Where my problem is is how to show a form to fill to the user which will depend on what choice he/she make from a dropDown menu.
Hope you better understand what I'm trying to achieve now. I will also follow your advise and search on deep linking using LINKTOFORM()0
Again thanks and don't hesitate if you want to add more...
Ok. I still can't picture what you mean by "It will open a form".
What is in the form? Does it only have ENUM column? Are there any other fields in the form that user needs to fill out? or is the form autogenerated?
@SignXi2 wrote:What I'm trying to achieve is to create a View where users can select activities in one dropdown menu
If it's a dropdown menu, then it's either a detail view with a quick edit column for the activities. But wouldn't you want to consider a different approach?
I think this should be the setup you need:
You need to have two separate tables.
Table 1 (Activities)
Activities : Key
Table 2 (Tasks)
Task ID : Key using UNIQUEID()
Activity: Ref Column - Point to Table 1
Remarks : or any other additional columns you want.
Then create an action in Table 1 "Go to another view within this app".
Formula should be a deeplink using LINKTOFORM()
LINKTOFORM("Task_Form",
"Activity", [_THISROW].[ACTIVITY]
"Remarks", "Whatever you want as default"
)
Now create a Deck or Card View for Table 1 and use the action as the Row Selected behavior.
Hi,
Again Thanks so much for replying. It helps me a lot to search and understand some concepts more clearly. Let me take another example to explain more clearly what I'm trying to achieve:
I have a table named Logs that log every activities in a company. That table has others tables referencing to some of its column. Basically when something happen in the company , an employee can log it, for example: "somebedy get hired in the company " or setting up a meeting... what I want is just one view with one dropdown menu and depending on what an employee choose in that menu, only informations related to that activity will be shown in a form to fill (a sort of dynamic form based on what is choosed).
if the employee select for example "Set up a meeting" in the dropdown menu, a form in the same view will appear with for example "the date, the hour, the meeting location, the name of the person to meet". if the employee select another activity for example, send a mail the form will change to: "the message, the receiver email and the object"
Hope yu understand now. I try my best to be clear as I can...
Thanks...
I think I understand.
If you are happy with "hard coding" this in the table, you can try:
Activities: Enum (List of different Activities)
Tasks: Enum (And then in Suggested values: SWITCH([Activites], "Activity1", {"Task1", "Task2", "task3"}, "Activity2", {"Task4", "Task5", "Task6"})
Hi,
Thanks for your reply. I will try that for sure and let you know if it works.
Again thanks and don't hesitate if you want to add more...
Try to read up un deeplink and LINKTOFORM(). It might help you.
Otherwise, a dependent action could solve it. It can fire LOG-data to your LOG-table on SAVE. (When saving new entries in another data table (eg. New employee))
User | Count |
---|---|
18 | |
15 | |
10 | |
7 | |
4 |