Skip to main content
Planview Customer Success Center

Resource Request Fields in the Project Team do not retain values

QUESTION
The configurable field behavior for resource requests seems very inconsistent.
-When submitting many resource requests with different configurable field values sometimes yield the same values for all requests usually from the last submitted request.
- A single resource request created in the project team section will often fail to retain the values after workflow is triggered.
- Empty code configurable fields need to be wiped out from time to time for the user to be able to select any value.


ANSWER
Users generally think the configurable fields are specific to each project team; they are not. The fields are only used as defaults when resource requests are created behind the scenes and are not specific to each project team; they are saved for the project only. We added informational text in version 2012 to help clarify that for users:

As a solution, users can set values for the fields – once, i.e. for the first project team they create against that project. Then, create the project team records and click the “submit request” checkbox, and don’t bother changing those UDF values, since they’re not specific to each project team. Once all their project team records have been created, save the project. That will create the resource requests. Then edit each resource request and add the appropriate UDF values. The UDF values cannot be set at the time they’re creating the project team record.
  
You may want to consider changing the resource request workflow, adding a “draft” status at the beginning. When the user is finished populating the resource request’s UDFs, he can change the status to “start workflow” (or whatever step is next), which will then start the workflow for that resource request. That would ensure workflow is not started by the job before the user is finished with the population of UDF values.