Parent record fields on a task form

[robinchadwick]

I have created an application to request the purchase of IT Infrastructure.

The application has a workflow that kicks off when the record is submitted.   The workflow creates several task records in sequence.

How do I get the fields from the parent record to appear on the form of the child task?

How do I make it so that when I change the field values on the task, those values populate the fields on parent record?

[JJ1 · Accepted solution]

You can add a reference field to the child record table which will refer your parent record table.Once the reference field is added to your child table,Go to Form Layout of child task table...you will see the Parent table name in green color with a'+' next to it.Click on it and add the fields of Parent record to your child record..Save layout.Now you can update the fields from your child tasks.

Hope this helps to meet your requirements

[dhasselquist]

In addition to what Jeevan posted, one of the requirements our implementation had was that it was captured at a certain point in time. In other words, if a person had an affiliation (a value we track on our user table) of student, and then became a faculty member, we would want to know what they were at that point for reporting purposes.

The only downside (as far as I know) to having the reference as Jeevan described, is it will only ever show the current value.

As an example, we created the field "affiliation" on the incident table. We have an on change client script for the caller field that will do an asynchronous ajax call to look up their affiliations, and populate it on the form.

As an example of the differences:

1. User A is currently a student. They create an incident. Using the method I provided above, the affiliation will be recorded as "student".

2. A week later, that person becomes a faculty member, and makes a request for a computer. The affiliation will be recorded as "faculty".

3. At the end of the month, a report is run breaking down incidents/requests by affiliation. This one user will be part of the stats for incidents for students and also part of requests for faculty.

If we used only the reference method, the incident record would appear to be for a "faculty" and not "student".

This could come down to business practice I suppose. For example, I can see where, using the method Jeevan provided, business phone would not need to use this process. You'd might only ever want to know their current number.