locked
AD Sync of Resources and Required Custom Fields RRS feed

  • Question

  • Today we discovered to our surprise that there seems to be an issue with synchronizing users from AD groups if any resource custom field is set to required. As it is a clear business requirement to enforce the setting of custom fields this adds something of an administrative nightmare when you have a large number of resources.

    Is this really as designed or do we have an issue with our installation?

    PS! Using SharePoint and Project Server 2010 RTM version. We are also aware that it is possible to develop custom code to raise events to fill the custom fields during sync, but there would then need to be processes to ensure that for every required custom field the data also exists in the AD.

    Regards,

    Stig

    Wednesday, July 14, 2010 2:26 PM

Answers

All replies

  • Since those custom fields are required, any sync will potentially add new resources, which must then be configured with the custom fields.

    I'd recommend not making those fields required but building a daily audit procedure in place to identify resource records not in compliance.  This could be done with a custom resource field and a custom view/filter in the Resource Center.

    Either that, or turn off the AD Sync (which can be more trouble than it's worth) and manually load resources from a spreadsheet.  That's not any harder IMHO than doing an AD Sync.  Once you've added them, the only extra functionality in the AD sync is that it'll move them from group to group if they change roles in the company - or remove them if they leave the company - but in that case, they would also have their login rights suspended which already addresses that need.

    Friday, July 16, 2010 12:32 AM
  • Thanks for the tips, Andrew.

    Seems quite logical to me that when a sync is provided this would use the default values for the custom fields. This could maybe be an idea for MS to provide on a later stage. In a large organization with distributed responsibilities it is not necessarily so that the persons who are adding users have access to the PWA to load resources. We have for example a two-step process for this. AD admins are responsible for adding users to the groups and PMO completes the setup of resources.

    Anyway, we will for now set the custom fields as not required and add a procedure for ensuring that the fields is being set.

    Thx, Stig

    Friday, July 16, 2010 8:17 AM
  • I would agree. That's not a bad suggestion to set the fields to the default
    in an AD Sync situation (or at least be able to select that as an option).
     
    - Andrew Lavinsky
     
     
    Friday, July 16, 2010 1:20 PM