Custom fields in “Project for the Web”
Custom fields in newly released “Project for the Web” at both project level and task level.
Thank you all for voting on this! Can you all share more about what you’re looking to do with custom fields?
What kinds of information would you put in them? Why?
Are you looking to only put them on tasks? Or, on projects and resources as well?
Do you want each field you create to appear in just for one project? All your projects? Would you be creating them for other people to use in their projects?
Thanks for your help,
The Project Team
I would like to add custom fields to calculate the predicted% of progress of tasks and projects. In order to have more reporting options with BI.
Rolly Perreaux commented
Without sounding too condescending, the same reasons why we currently use Custom Fields in Project Online (PWA). In either of these tools, we create and use custom fields to track anything that is not accounted for in using the standard Project/Task fields.
Tony Hitchcock commented
Custom fields would be great at Project level. This would allow an area to capture and report on more specific Project information (budget, project type, cost, Status).
Make the whole grid as flexible as Excel. One of the the reasons Excel is so amazingly popular is that its flexibility allows users to make use of it in ways/scenarios far beyond what Microsoft themselves could ever envision.
Microsoft should have a subset of fields are are required and locked down for scheduling (Start, Finish, Duration, Effort, etc) users then should be able to define and add whatever else they want. If we don't want scheduling we should be able to turn it off.
If you add this flexibility your clients creativity will see Project for the web become the standard across organizations just like Excel has and no one will be able to compete.
If you insist on locking it down and telling us what to do and how to do it (when the effort changes so does the duration) it feels like you aren't listening.
James Ward commented
I'll add that the roadmap needs more narrative - I'm looking to move our Excel-based NPI roadmap to this platform and it's not useful without a description of the project and ideally an image too to allow us to review with stakeholders
Andrew Sun commented
Custom fields to help group portions of work.
For example: A major customer project has 3 major deliverable products. Each of these will contain their own sets of tasks. The grouping will allow the project manager to group project by the deliverables, and in the end easily report on them individually or together as whole.
Another custom field usage is marking critical path/tasks.
Chris Kegler commented
It seems to me custom fields can be added in the CDS entity that is being used by Pftw. I, for myself, added various fields on Project level.
Chak Tukkadi commented
I agree, task level custom fields must to have for user adoption. I demo P4W in our organization and users are so excited to use this tool for small projects, but when they came to know there is no capability of adding custom fields at task level, now we are on hold. Please add this feature.
Tamara Frey commented
For most PM scenarios custom fields are necessary to ensure a proper Reporting / Classification / Grouping.
Though I understand that P4W should not become a copy of Project Online, at least the possibility to add project and task level custom fields to capture additional information not part of the standard setup for more sophisticated scenarios would be required to make customers use P4W
Antti Pajunen commented
Custom fields should go on projects and tasks at a minimum. Some data that is frequently in requirements: related entities (for example project risk custom entity), financials, customer field, milestone yes/no, EAC, ETC etc.
Fields from CDS entities
I don't think we should 'Custom Fields' as such but be able to add fields from the related CDS entities to the React GUI to ensure flexibility in what type of fields and their associated business logic. We should not try to replicate Project Online as that was not good architecture.
No use without custom field! This is so stupid not to make it by default!
nuno costa commented
We have to manage many projects from different Departments. How can we do that without "Custom Field"? This is a basic function.
The P4W represents a huge interface improvement but is not ready to be in Production Environment.
Curt Brasel commented
To monitor projected versus actual metrics (cost, timeline, resource hours, etc.).
We hope Project will be add custom field in Project level and User can filter by those custom fields on Roadmap. Due to we have a ton of project in Roadmap and wanna be quick filter by custom fields
For us, the information we would put into this kind of custom field would be information like:
Licensor Approval # (for easy lookup in the licensor's submission system)
Base Model (to track which kind of product is being designed/produced)
Factory (to be able to quickly filter for which projects are assigned to which external factory for production)
Color Code (Which set of paint colors are the primary colors being used for this project)
Projects would never be grouped by that information, because there are overriding priorities for grouping, but it would be amazingly useful to be able to designate what makes sense to have as top level information.
These fields would be project level fields and we would want to be able to customize them by template as not all projects follow the same specifications.
One of the reasons people use Excel to provide dashboards is that they can go in and add columns with project information as needed.
The reason they use excel to track tasks is for the same reason. They don't have to fight with it to get it to display the information they want and has the added benefit of being "free".
If they can't add fields, or it is frustrating to do so, they will revert back to Excel since it does what they want.
Dave Pritchard commented
P4W looks like a much better user experience but to be adopted custom fields are a must. Need these at task, project and resource level as we have in Project Online. Needed for reporting (management information system).
Excited to see where this goes and how long it takes to become available.
Keep up the good work.
If we are to move to P4W we need to be able to create custom fields for all the same reasons people use custom fields in MS Project etc.