How to make a Group_By Title, go to a Detail View of what that title represents?

Hello

In a Project Management App, the structure I made is that a Project has many Objects and an Object has many Tasks.

After I enter a Project from a Deck view of Projects:

I go into a Projects_Detail View, where I have the Tasks listed and Grouped by Objects.

Now itโ€™s really great that the Object Title, by which the Tasks are Grouped, is clickable. But the Issue is that when clicked, it takes me โ€ฆ somewhere unexpected:

By the Title, I know itโ€™s a Task_Detail Viewโ€ฆand itโ€™s empty because I got there โ€ฆ not by clicking a task so it doesnโ€™t know what to show (I think). I guess it goes somewhere related to a task view, as the name of the Object I click to get here, is a Grouping Name of the Tasks from the Task_Inline View.

But the question is, Can I make it take me to a Object_Detail View of that Object? (as the User would expect). Since itโ€™s not an action button, I have no idea where to control it from, and in the Task_Inline View, I canโ€™t find anything related.

And if itโ€™s not possible, can I make it unclickable?

Thank you,
Sorin

(I just have to say, this forum is incredible. Itโ€™s really alive and itโ€™s making the Appsheet learning curve so fast. I love it and I love the app. Thank you, really)

Solved Solved
0 22 2,415
  • UX
1 ACCEPTED SOLUTION

Quick update: we have a code-fix that will disable clicking on grouped headers like this. Eventually, we may decide a separate view that will list those grouped tasks but for now it seems sensible to prevent this drill-down because the rows are already listed.

Expect to see this fixed tomorrow afternoon.

View solution in original post

22 REPLIES 22

Any guess what it could be?

(I see there is a major issue going on and I guess Praveen is preatty busy with that)

Checkingโ€ฆ what kind of table structure you have? Is the Object a child record of Project and then again Task is a child of Object? No direct relationship between Project and Task?

Hy @Aleksi

So There is a Projects Table, a Objects table and a Task table.

The Objects Table has a Ref column to the Projects table, as each object is part of on Project and one Project can have many Objects.

And the Task Table has also a Ref column to the Projects Table and an EnumList Ref column to the Objects Table, which was constructed following these instructions I got from the community:

(point was when I add a Task from within an existing Project, I would have the Object question in the form already populated with the Objects related to that Project)

Whatever it is, clicking on something shouldnโ€™t take you to an empty view. So that is a bug. Could you please send the app name and repro details to support@appsheet.com

The data modeling is a bit non-standardโ€” it sounds like the same Task can reference multiple Objects within the same Project. So not too sure what it means to group Tasks by Object.

Hy,

What are the repro details and how do I get them?

Any task belongs to One Object and an Object can have many Tasks. It shouldnโ€™t be that a Task can reference more than one Object.

(so a Project can be like - Producing the furniture of a Coworking, an Object could be Producing a table within that coworking and a Task could be Cutting the wood for the top of that table. So any Task is related to one Object and any Object is related to one Project. Also, implicitly any Task is related to one Project. So in Project Detal View, I set to view the Virtual List Column of the Tasks related to that Project, which was created automaticaly by appsheet when I referenced the Tasks with Projects and grouped that view by Objects)

In that case, why not model simply as Task has a Ref to Object, and Object has a Ref to Project.

Then it should all work cleanly.

โ€œRepro detailsโ€ โ€” sorry I was using jargon. This just means tell us the steps to get to reproruce the problem โ€” which view should we click on, what should we click on next, etc. Your screenshots are very good though, so we may not need much more than that

@sorin_mihai I was thinking the same as Praveenโ€ฆโ€œwhy not model simply as Task has a Ref to Object, and Object has a Ref to Project.โ€

So you suggest taking out the Reference between Tasks and Projects?

Well, since itโ€™s my first app โ€ฆ I donโ€™t have a very frank answer I might be wrong.
But the thing is the views I created so far, are just so perfect for what I wanted when I started the App. So if you think I can reproduce them this way, sure. I made a copy of the app to try this new structure. So here are a few questions:

  1. Tasks are the core of the app since itโ€™s a task management app. Projects are the second most important. Objects are really something to group Tasks by, within a Project. So when I open a Project, I want to see all the related Tasks grouped by Objects, NOT the related Objects and then go into an Object and see just itโ€™s Tasks. Just like this:

2X_8_8ecaf96e54b5650db427a8a46b5d24b65ef1903d.jpeg

But if I take the ref between Tasks and Projects, how can I get this set up? I donโ€™t get the virtual column of related Tasks List which the I can choose to be displayed in the Projects View. I canโ€™t create a list column myself โ€ฆ

  1. In the deck view of the Task, I need the action button that if clicked, takes me directly to that Project view displaying all Tasks of that Project, grouped by Objects.

  2. In the deck view of a project, I want to have a button to quickly add a Task to that project, and when opening the form, have the name of that project already filled and only the objects belonging to that Project available in the dropdown. I donโ€™t want to go in the Project, than in an Object and then create a Task.


So really, itโ€™s like there are Projects, that have Tasks which can be grouped by Objects. But then again, an Object view is also really handy and so, thatโ€™s why itโ€™s not just a column in Tasks.
I took down the Reference between Tasks and Projects and Iโ€™m not so optimist. You think itโ€™s just a matter of working on it?

#1&2 - You could create the same functionality with your own virtual related list column like SELECT(Tasks[KeyColumn],[Project_ID]=[_THISROW].[ID]) and then group it by โ€œObjectsโ€.
#3 - You can create that action button with the LINKTOFORM(โ€œTasks_Formโ€,โ€œProject_IDโ€,[ID]). The dropdown for the Ref field can read Objects when you type it like SELECT(Objects[KeyColumn],[Project]=[_THISROW].[Project])

Sounds like a matter of working on it and learning more formulas Iโ€™ll take it.
Iโ€™ll be back with questions if I hit some dead ends doing this chage.

Thank you @Aleksi

What do you mean by โ€œIDโ€ in the last part of the formula?


So now the Tasks Table has a Objects ref Column referencing the Objects Table, and the Objects table has a Projects ref column referencing the Projects table.

The formula you suggest goes into the Projects table as a virtual column, and it wants to Select (and create a list) of the Tasks, where the Project ID is equal to the ID of the Project I just selected. But since the Tasks table does not reference the Project table, there is no Project ID in the Tasks table to equal the selected Project. However, in the Tasks table there is an Object - ID that references the Project - ID I just selected, but then the formula has to Select the Tasks (by their key column), that have the Object ID that references the selected Project ID โ€ฆ how would that go into the formula? โ€ฆ or am I mistaken?


As it is right now, your formula shows All Tasks listed on All Projects โ€ฆ (I replaced [ID] with [Project - ID] as it says " Error in expression โ€˜[Projects - ID].[ID]โ€™ : Unable to find column โ€˜IDโ€™ " and [Projects - ID] is the key)

Youโ€™re welcome

When you create a task record, you would need to have the projectID with the Deref like [Oblject].[ProjectID] as well so you can read the list. I was assuming you would have it already.

Quick update: we have a code-fix that will disable clicking on grouped headers like this. Eventually, we may decide a separate view that will list those grouped tasks but for now it seems sensible to prevent this drill-down because the rows are already listed.

Expect to see this fixed tomorrow afternoon.

Great, so coming back to the Initial Posting - The Group By Title is not Clickable and so it will not lead to an empty view anymore.

What I did to still have this link to the Object View, is I added an action button to the side of it and if clicked, it will take me to the correct view of that Object.

Problem solved Thank you

Any possibility to move that action button closer to the Group By Objects Title? instead of heaving it at the end of the line?

Hi,

I used to have what you call the โ€œObject actionโ€ button on my app. However, with this update that Appsheet has made, it has now disappeared!!! So can you please explain to me how you added the button? I canโ€™t seem to figure out how to attach it to the โ€œGroup by Objects Not Clickableโ€.

Thanks,
Josh

Hi Josh,

I also added that before the change and now it is gone too. Itโ€™s definitely related to the update to make the Group By Tile unclickable. So I donโ€™t have an answer anymore.
What I did now is I added the button as an Inlay button to all the Tasks so I donโ€™t go to the Object via the Group By Object anymore but I go through any Task that is Grouped By that Object.

Also the Bolding is definitely part of the Update and I like it as it gives the View of Menu and Submenu. I did that before through Format Rules but now itโ€™s automatic so I think itโ€™s great.

@nico @Aleksi

So just to be clear, in reference to this post what is called the โ€œobject actionโ€ is simply no longer available?

Not with the Group by when using Deck viewโ€ฆ Though you can assign that action to your โ€œDeckโ€ record.

@Aleksi Any hope to get this Action back? It would be very intuitiv to open the Parent by clicking on it.

Top Labels in this Space