app reference - "dynamic" filter
Hi guys,
I'm sorry if I am missing something here. I read about app reference filtering and we use it but I still feel it misses some important functionality.
I understand that I can create a view with a static filter like "where status = open". But what if I need a "dynamic" filter like "where company = my currently selected item" ?
E.g. I have a contacts app and a companies app. Every contact belongs to a company (i.e. has a reference) and all contacts are referenced automatically in the connected items. Now in the company app I want to have fields like "CEO" or "sales contact" where I want to reference one of the contacts which belong to this very company. I clearly cannot have a view for every company :)
Another example - we also have an app where all the branch offices are maintained. Each office belongs to a company. Now in the aforementioned contacts app I want to connect the person with the branch office she works at. Here again I want the reference lookup to only show branch offices belonging to the company the person works for.
Any idea how I can achieve this?
Cheers,
Andreas
-
Hi Charlie,
I am sorry but I do not quite understand your point. What you mean by "2 steps down"? I just want one filter - "show all contacts where reference = <somecompany>". The way it is implemented now I can only prepare a view with a static filter like "all contacts with status = happy", but this does not help here.
Another example - a "company" has many "offices". An "employee" has reference to "company". Now I also want to set the "office" where she works at - in the reference lookup I would now not want any office of every company we have in the system but only show the offices of this very company.
-
@Andreas for this I believe you would currently need to set up a branch office app and relate to that also, and then perhaps with a view of companies attached to it within the relationship field setting.
There are no current plans of adding something like this to the relationship field on the short term, but please do give more examples of uses and keep up the voting for it.
//Oliver - Podio
-
Hi Oliver,
at the moment I actually have such an "branch office" app (Company - can have multiple branch offices - employee works for company in a specific office). But the problem is as you suggested I would need a static view for each and every company in our Podio (and even in our small solution there are 200+). Not really feasible.
There are several use cases I could imagine. Basically also every case where you would implement "cascading lists" in a normal web solution. All kinds of long lists where we could filter the items we want on a criterion we have already selected.
e.g.
category -> products
group -> members
course -> students
country-> states
state -> cities
company -> offices
company -> employees
....Regards
-
forgot one very important use case for project management. e.g. if I would want time sheet recording or bug tracking,...
project -> tasks
project -> members
project -> deliverables
project -> bugsI would not want static views for all projects, but also not long lists with zillions of entries that do not make sense or are error prone (select member or bug of other project).
-
Upvote :)!
Indeed the same problem as https://help.podio.com/hc/en-us/community/posts/209685647-Relation-item-suggestions-filtered-on-dynamic-information-not-just-a-static-view-
Now as I already put in my post, knowing Podio a bit, it is very unlikely that you guys will build this.
But I just wanted to make sure before building it ourselves. So let me ask the question. Is this feature on the roadmap?
-
Pieterjan Muller - not on the roadmap! :)
-
@Sara Høeg Already thought so :).
Greetings from the Belgium (the chocolate ... and beer country -> maybe that's a good idea to bring along the next time I'm in Copenhagen?)
@Andreas: This was a first step for us to decide whether we put this on our roadmap. Now, just as Podio, we can't make any promises regarding the delivery of new features. Will certainly not be for Q2 (and likely also not Q3)
-
Yes, this would still be great! Very helpful in timesheets, if once a worker has selected the project they are working on, then the only deliverables to choose from are ones related to that project. We use standard deliverables for all projects, so if they don't remember to re-enter the project name in the deliverable field there's a strong chance of putting their time in the wrong project. Frustrating! Dynamic filters would solve this issue so easily that I can't explain to them why I can't implement it.
-
I need this too.
I have Modules and I have Business Objects. Business Objects belong to a Module.
I then create Projects which relate to Modules and affect a few Business Objects. So realistically defining the Module serves me no benefit when I am filling out the form as I still need to scroll / filter ALL of the Business Objects
Please sign in to leave a comment.
Comments
17 comments