Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Default value for drop-down list does not work for existing requests.

Highlighted
JudyZhu
Regular Collector

Default value for drop-down list does not work for existing requests.

We are using PPM 9.11.

 

In  a customzed project request type, there is a drop-down list with Yes/No values. In the related validation, the default value is No. Not set the default value for the field.

 

1. To create a project manually, the field will be set to No by default initially. However, if to create a project from a proposal, the field is blank. Why does this happen? Is it by design or bug?

 

2. After to set the default value to No for the field, the field of newly-created projects will be populated with No as expected. However, for existing projects, the field still left blank. Why the default value for the field does not work for existing projects? Is there anyway to have the field set to No from blank in all existing projects?

 

Judy

 

 

5 REPLIES
AlexSavencu
Honored Contributor

Re: Default value for drop-down list does not work for existing requests.

Hi,

1. Is there any chance that the field is populated by an Apply on Creation rule?

2. This is by design. If you make such a change, you should update the relevant requests in the database. Make sure you update the LAST_UPDATE_DATE column also.

3. Are you from HP Support?

Cheers
Alex

--remember to kudos people who helped solve your problem
Utkarsh_Mishra
Honored Contributor

Re: Default value for drop-down list does not work for existing requests.

Check the FIELD level security as well... generally such behavior is observed when there is field level security applied and action is taken by the user that is not part of the field security.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
JudyZhu
Regular Collector

Re: Default value for drop-down list does not work for existing requests.

Hi Alex,

 

We have not create Apply on Creation rule. With default value of field, it works for newly created projects, including those created from a proposal.

 

Which of my questions is your answer "by design" for?  Is it by design that if a field is set with a default valie, it only applied to newly created request,  instead of existing request? 

 

Judy

JudyZhu
Regular Collector

Re: Default value for drop-down list does not work for existing requests.

Hi Utkarsh,

Thank you for your kind reminder. There is no Field level security in this case.

Judy
AlexSavencu
Honored Contributor

Re: Default value for drop-down list does not work for existing requests.

Hi, Judy,

 

my answer ”by design” is for your second question.

 

cheers

alex


--remember to kudos people who helped solve your problem
//Add this to "OnDomLoad" event