Reference field from a relationship field
So I have an app for projects, and an app for deliveries ( actually trucks / material ). That being said I thought I could create a managed workflow to assign a billing task to the project manager of the project in which there was a delivery assigned.
Project App Contains:
Project Name: ( Text )
Project Manager: (Text )
Billing Date: ( Date )
... etc non specific to question
Delivery App Contains:
Delivery Title: ( Text )
Project Name: ( Relationship -> Project -> Project Name ( Text ) )
... etc non specific to question
In managed workflow I would like to create a task with as follows
Task:
Task Title: ( @Project Name + " - Billing" )
Due Date: Project -> @Billing Date
Assigned To: Project -> Project Manager
Things I have tried:
Calculation in Deliveries App to look up the billing dates/project manager from the project name relationship. I could only come up with "@all project manger" Which I didn't find helpful. Alternatively I thought that I could potentially cycle through "@all project manager" and see which one is related to the project name or something? But I wasn't sure how to go about that.
I explored the idea of just reassigning the project manager to the delivery but I didn't like that since I only want to input things in one location and relate them to each other. In this case the related item is the project name.
Additional notes:
I may be upgrading to the Plus account to get access to the advanced workflow if necessary.
Any help would be greatly appreciated if you need any additional information please let me know.
-
Hamid,
I have only been using this for about a week so this is all still a little new.When I put in the calculations field @All of project manager I get the error.
The script returned an unsupported result type.
I noticed in other question/post people used additional java script for loops etc. Do I need to loop through @all of project manager and reference the project name?
Thanks for your help on this.
-
To a dates fiemanipulafields Use http://moment.js documentation
-
-
Hi Zac,
honestly I don't understand what you want to achieve. If you want to have such a task in "Projects"
Task Title: ( @Project Name + " - Billing" )
Due Date: Project -> @Billing Date
Assigned To: Project -> Project Managerfor which reason you need a calculation field in Deliveries?? I think, you don't need any calculation field for that.
The projcet manager field in "Projects" should be a contact field, not a text field.
With Podio "normal" Workflows you can then create a task in "Projects":
If new item has been created,
create a task with title @Project Name - Billing,
assign it to the person in the contact field,
due date = billing date.Or do you want the task been created in Deliveries for each Delivery item? So that if you have 5 deliveries the same task is created 5 times? If so, you could do it with a workaround using Podio Advanced Flows.
What exactly do you want to achieve with a calculation in Deliveries?
Rainer
-
Rainer,
We have a number of projects going on at any one time so to ease the work for the project managers I wanted to create a task / flag /reminders etc so they project managers know what projects need to be billed for in that billing cycle. I figured if I created a task for each delivery / labor placing etc it would accomplish the task and eliminate the project managers having to search for what needs to be billed for each specific project.I have a backup plan if I can't create the tasks which would be to add a category to each delivery which is billed and having a custom view for Bill and filtered by project manager. I just thought the task idea was neat.
Thanks.
-
Hiya and forgive my intrusion. I noticed some references to .join() usage and I have tried using this in a calculation field like this: @Job Title + " - " + @All of Names.join() - but it is coming back with a script syntax error/unexpected token illegal. Both @ fields callups work fine on its own but putting this formula in place didn't. Sorry for going off topic!
Please sign in to leave a comment.
Comments
17 comments