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

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.

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.

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.

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.DenyAddAndCustomizePagesSet-SPOSite https://yourdomain.sharepoint.com/sites/OnePlan -DenyAddAndCustomizePages 0

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

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

RodFromm
Steel Contributor
Jun 21, 2024
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?
- Woody
  Copper Contributor
  Jun 25, 2024
  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.
  - jefmeyer
    Iron Contributor
    Jul 12, 2024
    Woody - Any update on this issue? We are facing the same issue.
- PaulB1810
  Copper Contributor
  Jul 16, 2024
  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.

Forum Discussion

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

Share

Resources