Traverse/lookup related items

Follow

David Schaap

• May 16, 2020 12:48

Setup:

Account > Contact > Ticket

In the Tickets app, I would like to filter and display the Account.

As far as I know, I can show the Account by first adding it in a calculation field in the contact, and then adding that one into the ticket, which works but is cumbersome (and you can't click on it).

I can also not filter on it in tickets. You end up having a stack that everything is directly connected to everything, just so that you have all the needed features. 

So ideally we can go multiple levels deep in Calculation fields, or add some kind of "Lookup" field that can do it.
Filtering wouldn't even need to go up multiple levels anymore if you could filter on these lookup-fields.

Please help us remain a happy Podio customer:) 

1

• 

  Nadège AUSTIN

  • August 04, 2020 14:53

  I need this too ! 

  0

  Comment actions Permalink
• 

  Adrien BLAISE

  • August 31, 2020 15:45
  • Edited

  Possible workarounds:

  1. Use WFA (Workflow automation, fka GlobiFlow)) to automatically reference the account within the ticket
  2. Momentum Power Tools let's you filter from related apps

   

  0

  Comment actions Permalink
• 

  David Schaap

  • September 01, 2020 19:59

  Hi, yes both workarounds sort-of work, but that means you're keeping data in-sync across items, which is unnecessary and a pain in the ass. I want access to the data, but not necessary copy it over.

  0

  Comment actions Permalink
• 

  Adrien BLAISE

  • September 02, 2020 12:59
  • Edited

  Adding/keeping parent account item within the ticket is no pain in the ass with automation workflow (the field can be hidden if needed). Incidentally, it can allow you to see all tickets related to an account (not just contact). 

  BTW, you definitely can make links to related items clickable within calc fields using markdown (e.g., the target app url + App Item ID).

   

  FWIW.

  0

  Comment actions Permalink
• 

  David Schaap

  • September 02, 2020 13:22

  Well what if I only want to use it once? Should I synchronise all data to the child-app just so that I can do the analysis, and then remove the field again afterwards? I would call this lack of flexibility a pain in the ass...

   

  David

  0

  Comment actions Permalink
• 

  Adrien BLAISE

  • September 03, 2020 07:48

  Not sure how leaving the field (possibly hidden) could hurt in this case.

  In fact, based on the setup description alone, I would strongly advise a client to link the related Account in all Tickets.

  Just like in all CRM/PM setups we have built (like Company > Contact > Project), the Podio user links a Contact in a Project, and we have a workflow that links the related Company too, so we can both get data/tallies/recaps at the company level, and filter projects by company. 

  But “your mileage may vary” of course ;) just FWIW.

  0

  Comment actions Permalink

Please sign in to leave a comment.