Forum Discussion
Custom Scripts policy breaks editing Custom Fields in PDPs (Project Online)
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?
- 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.
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.
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.
