Forum Discussion
Woody
Jun 20, 2024Copper Contributor
Custom Scripts policy breaks editing Custom Fields in PDPs (Project Online)
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 i...
Woody
Jun 25, 2024Copper Contributor
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.
- RodFrommJul 12, 2024Steel Contributor
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.
- PaulB1810Jul 16, 2024Copper ContributorTHANK 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. - jefmeyerJul 12, 2024Iron Contributor
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.
- NiblettJan 30, 2025Copper Contributor
Anyone have any new updates? I get extereme pushback whenver I ask to open custom scripts for a day anytime I need to update PO pages and they are reluctantly limiting me to once a month. Rediculous. Most of my frustration is that yes, MS sent out notices about custom scripts changes and, since I was concerned there were going to be impacts on PO, I scheduled meetings with Microsoft. I was told that there would be no impact to exisitng scripts in Project Online and that there would be no other impacts. Why did the PO team not know that the SharePoint script changes would impact PO pages? Why was there no communication? I know there have to be a bunch of large companies using PO since something as basic as timesheets are not available via the other MS tools, so why did this fall through the cracks? 😡