SOLVED

Project Detail Page (PDP) in Project Online not saving added fields when Stop Editing clicked

Copper Contributor

Hello friends. I've encountered a strange situation in which I am editing a PDP in Project Online that I've customized in the recent past. I wish to add two Enterprise Custom Fields to a Basic Info web part.

 

I follow the standard steps of Edit Page > Edit Web Part > click the Modify button for Displayed Project Fields > select the two fields and click the ">" button > click Apply and confirm they show in the web part > click OK to commit > click the Stop Editing button. 

 

The page then defaults back to the previous state. I logged into two different browsers, cleared cache, and turned on the Versioning settings for the library, using Check In and Out, then reverted back to No Versioning. 

 

I will be checking with other admins to see if they have the same outcome tomorrow, but wondered if anyone else had experienced this situation? 

 

 

7 Replies
Bud --

Hmmm. What you are describing sounds very similar to this recent thread:

https://techcommunity.microsoft.com/t5/project/custom-scripts-policy-breaks-editing-custom-fields-in...

Do you think this might explain what is going on with your tenant? Please let us know what you find. Thanks!
Thanks, Dale! That sounds likely and I'll follow this path. Appreciate the quick follow up!
Bud --

If my recent reply ends up solving your problem, please return to this forum and let us know. I am perplexed at how this custom scripts policy could "break" the editing of PDPs, but if that is the root cause, we need to know. Thanks!

@Bud_Ratliff - We are seeing the same in all the PWAs in our tenant.  I have a ticket open with Microsoft and I would suggest you also open a ticket.

best response confirmed by Dale_HowardMVP (MVP)
Solution

@Bud_Ratliff This issue was caused by a changed Microsoft implemented to remove custom scripting from OneDrive and SharePoint.  You will need your Global SharePoint Admin to go M365 Message Central and review Message ID MC714186. Basically, they will need to run a PowerShell script to re-enable custom scripting on affected PWAs.

Thanks, Rodney! And thanks, Dale, for marking this as the answer.

@Dale_HowardMVP  @RFromm - The issue is resolved now that the administrator re-enabled custom scripting on our instances. Thanks!

1 best response

Accepted Solutions
best response confirmed by Dale_HowardMVP (MVP)
Solution

@Bud_Ratliff This issue was caused by a changed Microsoft implemented to remove custom scripting from OneDrive and SharePoint.  You will need your Global SharePoint Admin to go M365 Message Central and review Message ID MC714186. Basically, they will need to run a PowerShell script to re-enable custom scripting on affected PWAs.

View solution in original post