20.04.2015 - Filter in relationship field

Follow

Oliver Wray

• April 20, 2015 15:13

You can now choose which of your items that will be pickable in a relationship field. You do that by selecting one of your saved views from the related app when modifying the template. This can be just projects with the status 'Open', or just 'Current' events for example.

This will give you a better way of archiving app items and decide only to have active items show up in your relationships.

2

• 

  Victor MOREIRA

  • April 20, 2015 21:46

  Nice Addition. Keep up with good work guys.

  0

  Comment actions Permalink
• 

  Heather Fox

  • April 21, 2015 01:20

  Hooray! Thank you.

  0

  Comment actions Permalink
• 

  Roger Jesrani

  • April 21, 2015 02:37

  Hi Oliver,

  One interesting side product of this (I think, I'm still testing it) is that you can now sort the items in the drop down relationship list by pointing to a sorted view. Before this, the sort order was a little strange defaulting to the order records were last touched.

  0

  Comment actions Permalink
• 

  Roger Jesrani

  • April 21, 2015 02:41

  Testing a little further, this seems to be the case. I tried reversing the sort order of the view and sure enough the items in the relationship drop down reflected this. Nice!

  0

  Comment actions Permalink
• 

  Roger Jesrani

  • April 21, 2015 02:55

  What are the implications (if any) of whether or not the selected view is a Team view vs. a private view. If I select private view, will others still see the filter/sort of the relationship field items? Thanks

  0

  Comment actions Permalink
• 

  Adil Tuncer

  • April 21, 2015 11:00

  I could not find where to select category field like "open" , "closed", etc.

  0

  Comment actions Permalink
• 

  Roger Jesrani

  • April 21, 2015 17:18

  I think what Oliver is referring to is when you create your view, you can filter on any fields in the associated App (table). So if your App had a status field (for example), you could use it in your view.

  0

  Comment actions Permalink
• 

  Heather Fox

  • April 21, 2015 22:49

  Thanks, Roger, for the heads-up about sorting. Very neat!

  I have tested a private view and it was visible to the team in the relationship field, with options able to be selected.

  0

  Comment actions Permalink
• 

  Roger Jesrani

  • April 22, 2015 00:04

  Thanks Heather! Good to know that the filtering still works for everyone even if the view is private.

  0

  Comment actions Permalink
• 

  Ann Donnelly

  • April 28, 2015 14:52

  I was very excited to see this and applied it straight away, but then our staff started having problems finding the item they wanted to select. I have a number of relationships set up and only one has a filter, as it's the only with archived items. The item we wanted to select would only come up if we copied and pasted the name from it's original record - i.e. General Medical Annual Accounts y/e 31 December 2014. It didn't come up if we typed part of the title - i.e. General Medical Accounts 2014. In once case we weren't able to select the right item because there were a number of items showing from the unfiltered relationships and the one we wanted was at the bottom, below the bar where you'd click to save the item.

  0

  Comment actions Permalink
• 

  Monir Mohammed

  • May 04, 2015 22:05

  Is it just me or does this NOT take in account the 'options' columns ... the basics seems to work, filter and then have it selectable in a relationship ...

  I have a view which has say 4 columns, a create a new view and remove column 1 and I am left with 2,3, and 4 only. Now when I setup a relationship in another app and reference the new view I get a filtered list but it sorts the list and only allows me to view it with column 1 .. any ideas why that is or have I got the expectation wrong?

  0

  Comment actions Permalink
• 

  Chris Webb

  • June 23, 2015 08:22

  Is possible to filter a child app by a parent app's view? The example is that I only want to display the candidates that are associated with "open" job positions.

  0

  Comment actions Permalink
• 

  Stefan Ukena

  • June 23, 2015 09:16

  Hi Chris,

  yes, that's possible by adding a calculation field in the candidate app. Let's say your job-app has a field Job Status which can be "open" for open positions and anything else for filled positions. Then the calculation in your candidate app would look something like this (note that this also assumes that each candidate is only linked to a single job):

  var jobStatus = @All of Job Status[0];
  
  if (jobStatus === 'open') {
    1;
  } else {
    0;
  }
  

  A shorter version would be:

  @All of Job Status[0] === 'open' ? 1 : 0
  

  In both cases the new calculation will show either 1 (for open jobs) or 0 (for all others status values). You can then create a filter in your candidate app that only shows candidates that have a value of 1 in this calculation field.

  Best,
  Stefan

  dieKollaborateure.com - Podio Training+Consulting+Development English & Deutsch

  0

  Comment actions Permalink
• 

  Chris Webb

  • June 23, 2015 11:12

  Hi Stefan,

  That worked a treat! thx

  0

  Comment actions Permalink
• 

  Andreas Forstinger

  • July 31, 2015 08:18

  Hi guys,

  just trying to again promote my request to further improve this feature with possibility of passing dynamic values. So filter the referenceable items based on field value of the currently selected item and not only a static view with fixed filters.

  Examples: only choose employees of currently selected company, only choose offices of currently selected company, only choose cities of current selected country,...

  https://help.podio.com/hc/communities/public/questions/204279178-app-reference-dynamic-filter

  With this we can actually implement kind of cascading drop downs.

  Regards,
  Andreas

  1

  Comment actions Permalink

Please sign in to leave a comment.