none
Required ECF and PDP's-Unable to check in project RRS feed

  • Question

  • Our organization has multiple Enterprise Project Types. The PDP's differ for each Enterprise Project Type. We have several required ECF's that we add to PDP's. Not all required ECF's are part of the PDP's for each Enterprise Project Type. We are having an issue where we are unable to check in a project after project creation due to project server requiring data for an ECF that is not part of that project types PDP. The only solution I have found at this time is to only make an ECF mandatory if it exists in a PDP for all Enterprise Project Types. Any advice would be appreciated. Thank you!

    Example: Sponsor is a mandatory ECF that is added to our standard project initiation PDP. This ECF is not added to any PDP's for our non-standard project, we cannot check in a non standard project because it is requiring "Sponsor", yet this ECF is not part of any PDP for our non-standard project.

    Tuesday, July 3, 2018 7:33 PM

Answers

  • Hi Tyler, 

    The issue that you are facing is a common one that even we faced. Yes, the "required" fields will have to be included in all Enterprise Project Types, unfortunately. If there is a way to reconcile the required fields in some common fields, then you should do that. Other than that --

    1. Have you considered using Workflows for your different PDPs? Workflows in Project Server open up the option of setting required field per stage. So, you could technically have 3 required fields in Standard project and have 3 entirely different fields in Non-Standard project. The workflow does not have to be anything complex, it could be absolutely one step wf - Start the workflow --> Log a message "Workflow Started" --> Stop the workflow. 

    2. The other option is to have a visual indicator only for each required field. That is, instead of having a hard check on the page, you can set up the field as "Sponsor* " with the little asterisk mark so users know that it is required. If you or someone in your group is good with JavaScript/CSS, you can "color" the asterisk red. 

    Other than these two options, the only one you are left with is to evaluate all required fields and reconcile them. 

    Thanks,

    Abhi

    • Marked as answer by Tyler-NTDP Thursday, July 5, 2018 3:24 PM
    Tuesday, July 3, 2018 9:29 PM

All replies

  • Hi Tyler, 

    The issue that you are facing is a common one that even we faced. Yes, the "required" fields will have to be included in all Enterprise Project Types, unfortunately. If there is a way to reconcile the required fields in some common fields, then you should do that. Other than that --

    1. Have you considered using Workflows for your different PDPs? Workflows in Project Server open up the option of setting required field per stage. So, you could technically have 3 required fields in Standard project and have 3 entirely different fields in Non-Standard project. The workflow does not have to be anything complex, it could be absolutely one step wf - Start the workflow --> Log a message "Workflow Started" --> Stop the workflow. 

    2. The other option is to have a visual indicator only for each required field. That is, instead of having a hard check on the page, you can set up the field as "Sponsor* " with the little asterisk mark so users know that it is required. If you or someone in your group is good with JavaScript/CSS, you can "color" the asterisk red. 

    Other than these two options, the only one you are left with is to evaluate all required fields and reconcile them. 

    Thanks,

    Abhi

    • Marked as answer by Tyler-NTDP Thursday, July 5, 2018 3:24 PM
    Tuesday, July 3, 2018 9:29 PM
  • Thanks Abhi. I think the visual indicator will work well for us. 
    Thursday, July 5, 2018 3:24 PM