Skip to main content
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Problem with resources' non-working days

  1. Last updated
  2. Save as PDF

Symptoms:
Working days had been adjusted for all resources and global workgroups, so that each resource record has the same non-working day setting as its global workgroup. For example, certain gobal workgroups have Friday and Saturday as non-working days, and the same setting is used for all resources under this global workgroup.

After updating some resource records via API (updated fields are not related to non-working days) , some resources returned to the default Saturday/Sunday setting, causing resources to have 3 non-working days in a week (Friday/Saturday due to the global workgroup setting, and Saturday/Sunday due to the resource setting). Why has this happened, and how can we correct data and prevent this from happening again?


Reason:
When a resource record is updated by using Resource.Update() method, the non-working days for the updated resource is reset to the default value Saturday/Sunday, if a non-working day value is not provided while updating the resource record.

This is a defect in v2010, and has been fixed in Changepoint version 2012.
 

Resolution:

Set the non-working day of a resource whenever the resource is updated via API, so that it is not reset to the default value by API.

If the non-working day settings at global workgroup level are the same as resource non-working day settings, the non-workingdays for all resources can be set to “0000000” via API as an alternative method (whenever the resource is updated via API). In that case the resource profile would not have a non-working day therefore the global workgroup non-working day settings would apply.