Can a report show information from a predecessor?

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered

I have an Assignments and Assignees table.  Assignment #1 is a predecessor of Assignment #2.  Assignment #1 & #2 are done by two different Assignees. 

I would like to run a report for for Assignee #2 and show them who completed Assignment #1 (the predecessor).  That way they know what kind of mess they are getting into.

I tried to push down the predecessor field to the Assignees table as a lookup field but it's not showing it as an option. 

Photo of Carlos

Carlos

  • 100 Points 100 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of Scott

Scott

  • 334 Points 250 badge 2x thumb
Hello!

Unfortunately from what you have told me, I cannot accurately picture your table structure in my head.  I assume because you are unable to create a lookup field that your tables are assigned so an Assignee may have many Assignments, meaning that you can't link the same data backwards onto the Assignee table as you would from the Assignee table to the Assignments.  You would need to create another relationship between the two tables so that an Assignment may have many Assignees.  Since you already have a relationship set, you could use an existing field as your reference for the new relationship.  

Again, I don't know your table structure.  If you would like a more accurate response, please list a detailed structure and how everything is laid out and I will get back to you with a more accurate response.

Regards,

Scott
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 65,310 Points 50k badge 2x thumb
I don't think we will be able to pull information from Predecessors into a subsequent task.
Photo of Jack

Jack, Champion

  • 50 Points
Carlos,

Updated Answer:
I just built a test application and can confirm both the below work.
Here are the steps to take:
Option 1 using api and button clicks:
Create a numeric field and call it for example previous assignment.
Create a formula url field (button) with the following formula:
URLRoot() & "db/ASSIGNMENT TABLE ID" & "?act=API_EditRecord&rid="&[Record ID#] & "&apptoken=YOUR APP TOKEN" & "&_fid_11="&(ToNumber(ToText([Previous Assignment]))) & "&rdr="&URLEncode("THE URL FOR THE PAGE OR REPORT YOU WANT THE USER TO BE DIRECTED TO")
Please swap out the sections in capitals to match your app specific details and change the field ID to the field ID of your predecessor field.
Create a relationship assignment < assignment and choose the reference field as previous assignment.
Then use the lookup to pull through all required fields.
The one caveat with the above method is that when adding a new assignment the record must be saved before you can execute the button call.
Option 2 using form rules:
Create a numeric field and call it for example previous assignment.
Create a formula numeric field and call it previous assignment number and use formula below: ToNumber([Previous Assignment])

Then create a form rule: When the record is saved Change previous assignment to the value in the field previous assignment number
Don't forget to un tick the fire change box, so that it fires each time, in case you change the predecessor.
Create a relationship assignment < assignment and choose the reference field as previous assignment.

Then use the lookup to pull through all required fields.
Hope this resolves your issue.
Jack
Photo of Carlos

Carlos

  • 100 Points 100 badge 2x thumb
Jake,

Thanks for the reply.  It was a nice idea but it doesn't seem to be working.  When I establish the relationship and go to select the reference field, the Predecessor field is not an option.  It's not even showing up as a Lookup field option either.  I don't know if you have any other possible idea.
Photo of Carlos

Carlos

  • 100 Points 100 badge 2x thumb
Thank you for your replies.  In regards to the table structure, Projects ∈ Assignments ∈ Assignees.  For simplistic purposes, a Project typically has 2 Assignments (the main step and a review).  Typically there is only 1 Assignee per Assignment.
Photo of Jack

Jack, Champion

  • 50 Points
See below
Photo of Jack

Jack, Champion

  • 50 Points
I've updated my above answer with 2 working solutions.
Photo of Carlos

Carlos

  • 100 Points 100 badge 2x thumb
Thank you for the detailed reply.  Unfortunately, I'm not sure if this is going to work for me.  I use a copy master and details button that involves the Assignments table.  When I created the relationship to itself, it made a looping relationship which the copy master button doesn't seem to like.  The copy master button is more important that seeing predecessor information in a report so I think we've come to a dead end there.

That being said, I can still push down the predecessor number from the numeric formula field that I created so it can be seen in the Assignee table.  So in certain regards, the information is in the Assignee table to complete the report.  If I export the report to Excel, I would get the information I need by doing an INDEX MATCH formula.  I'm trying to figure out what would be the equivalent of that (if any) in Quickbase.
Photo of Jack

Jack, Champion

  • 50 Points
Carlos,

What I indicated above (previously) is probably the closest to match and index natively in Quickbase and would work without the copy master records/details. There may be the possibility of writing some Javascript to do this (not currently my area of expertise). If you want to explore this, then it would be advisable to start a new post mentioning javascript/jquery in the title.

Sorry I couldn't resolve your issue fully.

Jack
Photo of Carlos

Carlos

  • 100 Points 100 badge 2x thumb
I greatly appreciate the effort.