Custom fields in “Project for the Web”
Custom fields in newly released “Project for the Web” at both project level and task level.
Chris
shared this idea
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
25 comments
-
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.
-
Gabriel
commented
Fields from CDS entities
-
Anonymous
commented
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.
-
ivan
commented
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.).
-
Lip
commented
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
like:
Project type
Project budget
etc.. -
Caitlyn
commented
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.
-
Michael
commented
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. -
Anonymous
commented
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.
-
Anonymous
commented
It's definitely a no go if custom columns are no available. We use it to keep it centralized/standardized for business units to use it and to generate the respective PowerBi reports. If P4W is the future of MS Project, this should really be considered.
-
lisette pieke
commented
Custom fields on project level, so we can enter the project code when creating a project. We use this to link the information out of dynamics and project in our power bi overviews.
-
Stephen Little
commented
Project level: Absolute must is a field which provides the same function as department in Project Online. Also project classification / Scale / Type etc
Task level: Repeating what was said by Dave Jones, replicate the custom field functionality that project Online has.
Many examples of custom fields but just picking one area; cost management and purchasing:
* PR or PO reference number and associated value;
* Change Request (CR) number reference and associated value.
* Calculations (and can roll up). e.g. (PO Value + CR Value) - (Actual + Remaining cost) .
Also RAG status indicators please. -
Dave Jones
commented
Look at the way Project Online works. Replicate that in Project for the web. Allow the creation of custom fields at the project, task, and resource levels. CRITICAL functionality. Further, values should be calculated, limited to a set of options (e.g. a pull-down), or user-entered. Again, Project Online is doing this VERY WELL, and there's no need to reinvent a great idea. Just replicate it and make it better.
-
Michael
commented
In terms of project for the web we would just require task and project level fields. Resource level project fields are only really needed for more sophisticated management
-
Peter
commented
I use custom text fields to categorise tasks for reporting purposes in PowerBI. There are very few other features specific to Project Online that I require so I'd love to be able to use the far more lightweight project for the web, but I can't switch over without custom fields.
