Forum Discussion
Custom Scripts policy breaks editing Custom Fields in PDPs (Project Online)
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.
- 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. 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.
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? 😡
There was communication both from the Message Center back in February 2024, and I also (when I worked for Microsoft) wrote this blog post. Don't expect any more changes or new communication in this area - nothing is going to revert this. https://techcommunity.microsoft.com/blog/projectsupport/project-online-sharepoint-custom-script-control-impact/4225571
Best regards,
Brian
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.- 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.
- It's also interesting MSFT didn't exclude PWA#0 site templates. That seems to be a better long term solution.
