Custom Scripts policy breaks editing Custom Fields in PDPs (Project Online)

[Woody]

Hi!

Due to the recent policy applied by Microsoft about blocking the edition of Custom Scripts with the CEWP, we cannot edit Project Details Pages anymore to add/remove Enterprise Custom Fields in Project Online.

This should be working as Enterprise Custom Fields are not Custom Scripts!

Any advice?

Thanks in advance

[#2]

@Woody In our tenant custom scripting must enabled to modify the PDP (web part) and I have recently modified a PDP.  Have you talked with your global sharepoint admin to see if they need adjust a policy or configuration in your tenant?

[#3]

@RodFromm 

What is the relation between adding or removing ECFs to a PDP and Custom Scripting? 

I cannot see why a basic Project Online functionality is impacted by the recent Custom Scripting policy. We cannot work by opening a ticket to disable the policy every time we need to modify a PDP to add or remove a ECF with no use of Custom Scripts!

Additionally, Site Collection Content Types are not editable anymore, so if you use a Word file as a template for CTs, you cannot edit it anymore.

All due to the Custom Scripting policy.

[#4]

@Woody - Any update on this issue?  We are facing the same issue.

[#5]

@jefmeyer Review this. Microsoft implemented a change that removed 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.

[#6]

@RodFromm - I understand how to revert the script setting, however this doesn't seem to be a good long term solution.  If I understand correctly, it's possible to delay this change, but come November 2024, the script blocking will be enforced and then it will require SP admin action to revert for a 24 hour period.  Since this seems to be a limitation of the Project Online web parts, are there any available or planned updates to Project Online to address this?  If not, this seems like a nail in the Project Online coffin.

[#7]

It's also interesting MSFT didn't exclude PWA#0 site templates. That seems to be a better long term solution.

[#8]

@jefmeyer It doesn't sound good.  While I don't like it, I don't spend a lot of time each month editing Web Parts in MS Project Online, so setting up a process to have the global admin run the script when needed wouldn't be so bad. 

My bigger concern is Microsoft continues to role out these "updates" that make it more difficult to use Project Online. If Microsoft would just implement some key functionality into Planner Premium (Project for the Web): redo security roles, custom global fields, cost fields, resource rates, increase number of tasks to 10K and add timesheet functionality I believe a lot of groups would migrate to Planner.

[#9]

I noticed the same change in my personal O365 Tenant as well. It looks pushed out by Microsoft vs a change from the work Project Online instance.

[#10]

THANK YOU!!
This is the fix that @RodFromm and @jefmeyer were referring to. It works for editing the PWA Home Page as well as additional web parts for the PDPs.
1, In O365 Admin, go to the SharePoint Admin portal
2. Click on Active sites
3. Click on the site name for MDTAProject PA Site Name
4. When the dialog appears, click on Settings
5. Under Custom Scripts, click Edit
6. Select the Allowed radio button and click Save

The Allowed setting will default back to Blocked after 24 hours.

[#11]

There is a fairy tale about a bear trying to pick up food from crops. When the bear picks up more, more falls from its hands. That is what Microsoft keeps doing, unfortunately.

[#12]

Update it only for the specific site collection instead for the whole tenant.

Connect-SPOService -Url https://yourdomain-admin.sharepoint.com/ -Credential email address removed for privacy reasons
$url=Get-sposite -Identity https://yourdomain.sharepoint.com/sites/pwa
$url.DenyAddAndCustomizePages
Set-SPOSite https://yourdomain.sharepoint.com/sites/OnePlan -DenyAddAndCustomizePages 0

[#13]

Yes, this is the PowerShell equivalent of what can be done in SP Admin Center. Just be aware that this setting will revert after 24 hours.