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 for your continued feedback here. We are working on enabling you to create and use custom fields in Project for the web.
While we don’t have an ETA quite yet, we will provide one as soon as we can.
As always, let us know if you have any more feedback (on this suggestion, or other suggestions).
I see that custom fields are being rolled out now. Any plan or ETA that when custom fields would be available for Power BI to use them in reporting?
Need to include links to other Office documents (OneNote, Excel, Word, etc).
The last update was back in the beginning of May. It's been almost a quarter now. Is there any update on when this feature will be available?
The custom fields should be in a text, number or date format. the column for this should be able to appear in the grid and these fields made available within Power BI.
Any custom field that we create in Project professional should be viewable in Project online/PWA(when published) and should be able to bring the custom field in the PowerBI report as well.
This is such a basic requirement. I need to be able to add in basic information such as Governance group, Status etc
You make a good data for me and your website is best posting.
I accept there are numerous who feel a similar fulfillment as I read this https://www.webhostingscoupon.com/hostinger-promo-codes.html article! I trust you will keep on having such articles to impart to everybody.
Need the ability to map a project to a record in Dynamics 365 so that I can connect them in the data model with Power BI. So, ability to have a custom field at the project level to enter a unique ID (or autopopulate from Dynamics) that is common in both places is what I was thinking.
Matt Griffin commented
I'd like to be able to create a custom field with a drop down option, my specific scenario is a Yes/No option and to default to 'No' or null. This way I can use Power Automate to kick off other things based on a task being flagged 'Yes'
Adrienne Radesky commented
A custom field for "Department" would be helpful to build a portfolio of projects.
I know Project for the web is supposed to be basic, but can you implement the possibility to add $ costs and consumption calculations (not just resourse usage?) per line item as a new field? It would be a great help to be able to calculate burndown consumption at a given date during the plan.
Is there any idea of an ETA on this?
Brandon Casas commented
This is definitely a necessary option if our team is to consider Project for the Web. Thanks for planning it. Hope to see this feature soon.
Chak Tukkadi commented
Thanks for considering our feedback. I hope you are planning to build Project level and Task level custom fields. Project custom fields are helpful to manage project metadata like "Project cost center, Project budget, Department name" etc. One of the usage of task custom fields I think as below:
As we know, there is no baseline feature, so PMs can define additional custom fields to track the variance of task against standard fields like start date and finish date etc.
Process will be, prior to project execution, PM enters same date in both fields task start date and also on custom date field (Example: "Base Start"). This the where PM and client agree for project timeline. As project progress, PM will make update to default field start date as needed without changing Base Start. This way, we can see the variance of task. Similar process will apply to other fields. This way we can replicate baseline functionality in Project for Web.
Agree with those saying, it needs to be flexible, but to give you an idea, we need to include the functional group that is doing the work. Something may be assigned to a person, but we need to be able to indicate whether that person is on Operations, Creative, etc.
We use custom fields extensively, both internally and for clients. I have yet to see a client who did not require a custom field in Project Online, and we consistently see them at the Project, Task and Resource Level. Gotta have custom fields!
Definitely on Projects to indicate project status according to desired frameworks (prince2 stages etc).
Every organization is different and has slightly different needs and naming conventions. Custom fields allow great flexibility and also allow for helping with change management by keeping familiar names. We use them 100% of the time!
Custom fields help us with all sorts of different projects/tasks/resources. Not all of our users should be expected to go into the PowerApp/CDS to make all these sorts of changes. Defeats the purpose of having an easy to use project tool.