Comments

4 comments

  • Joseph Espinoza

    Hi Vincent,

    Thanks for the suggestion! If you find yourself doing this more often than not, would it make sense to move the relationship field to this app instead of the one that's referencing it? Can you give a little more info about your use case where this would come in handy? Thanks!

    /Joseph – Podio

    0
    Comment actions Permalink
  • Vincent Poirier

    We would use both sides. Usually, when we create a Deliverable, we select the target parent Project (normal relation field). http://oi57.tinypic.com/259xy4o.jpg That way, we can see the associated items in the project and if we have to modify any deliverable, we can open them first and proceed (linear workflow).

    This option would come in handy in a few situations when we're looking at the project and thinking about creating a new Deliverable. It would open the window right away (with or without the relation field populated accordingly, saves time one way or the other) instead of closing the Project, opening the Deliverables, clicking add a Deliverable.

    I definitely wouldn't put this on the top list, we have our own "Podio Wishlist" at Magik Web and this feature is just a "nice-to-have".

    ~Vince

    0
    Comment actions Permalink
  • Jean-Claude Massé

    It's seem like something i ask for in a private request. It's based on similar feature found in others apps that have relationship fields.
    Mostly of the time, there is 3 type of relationship:
    One-to-One - Both modules' records will contain relate fields.
    One-to-Many - The Primary Module's record will contain a subpanel, and the Related Module's record will contain a relate field. (like now in podio)
    Many-to-Many - Both modules' records will display subpanels.

    0
    Comment actions Permalink
  • Joseph Espinoza

    Thanks Vincent and Jean-Claude for your feedback. :)

    /Joseph – Podio

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk