I am making a page with 3 custom collections. Collection one shows status 1, collection 2 shows status 2, collection 3 shows status 3. In each of the steps of the workflow I want people to be able to change the data in column X, Y and Z. And yes, all are writing to the same column. But since I am 1 person editing, I can only edit in one collection at a time. Glide doesn’t allow me this because I am writing multiple times to the same column.

How could / should I do this different?

I don’t follow. Can you explain with context what the user is attempting to do? What’s the workflow?

1 Like

See it as 3 collections filtering on todo / doing / done. With a choice component the user changes status and in every filtered collection the user should be able to change written info like size.

I’m not following either. Can you explain the problem in more detail? I’m not sure I understand where you are running into trouble.

1 Like

I also read this last night and decided that it would have been too much mental strain to try and understand what you’re asking for, so I passed.

I think some screen shots would help.

1 Like

Interesting, my mind seems to work in a wrong way. To me this is logical :slight_smile:

So I want people to visibly move from status to status with the possibility to change data in every phase. How would you do that?

If you focus on the “not allowed” part there, it’s not really restricting you from doing your work, more like a warning that you might not want multiple components writing to the same field on the same screen. You can still do that.

1 Like

Yeah, I do this a lot of times. Slightly different from your scenario, but sometimes I want both a choice component as well as a text entry to both point to the same column. This is to allow the user the option of either choosing from a list of existing items, or write in their own choice. Of course I get the red warning when I do this, but it doesn’t stop me from doing it.

It’s just a red warning. Nothing in the warning says you are not allowed to have multiple components pointing to the same column, and nothing is stopping you from doing it. It still works, correct?

1 Like

Ah ok! I didnt try! Didnt dare to! Then no problem :slight_smile:

1 Like

Ah, the red color stopped me from trying! Thanks

1 Like

I’m not sure I follow.

Recently I built an issue tracker, where the basic experience is the ability for users to submit an issue. The initial issue had a ToDo status. The second part of the experience was a second set of users, let’s call them MaintenanceStaff, could see a collection of the issues, grouped by status type, and with the click of a collection item action they could change the status of each issue from ToDo to Doing to InReview to Done.

My setup:

  • One single collection (not multiple). On a given tab, I prefer having fewer collections, especially if these collections are simply different views of the same data.
  • Grouping within the options of the collection. I grouped along a template column so the groups and issues didn’t bounce around the screen.
  • One single custom action ‘Change status’ with a few logical branches to move the status along and down the screen. This custom action is just a bunch of ‘Set column values’. On a kanban board this would move an issue to the next column right. If you dislike or are uncomfortable with conditional branches in a custom action, you could create a series of simpler custom actions, use all of them as collection item actions and set conditions there. This latter method allows you to have different names for each action rather than a generic ‘Change status’.
1 Like

Problem was solved since knowing that it is allowed to write to the same column more times in a page!


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.