Everything Was Working Fine… Until It Wasn’t
For many organizations, Project Online (PWA) has long been the workhorse of portfolio visibility, governance, and status tracking. And over time, it became “homegrown.” Custom scripts. Script Editor web parts. JavaScript buttons to auto-fill fields. CSR to make forms prettier.
But recently, something changed — quietly.
Microsoft has blocked custom scripts by default in SharePoint Online.
And if your team has been noticing errors in Project Detail Pages, missing field logic, or mysteriously broken workflows… this is probably why.
See Microsoft’s official announcement: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script
What Broke and Why?
Custom scripts in SharePoint have always lived on the edge of supportability. But now Microsoft has put their foot down:
- Site collection admins can no longer use Script Editor Web Parts by default
- Pages using JSLink or JavaScript injection may fail silently
- SharePoint Designer workflows relying on these elements might also behave unpredictably
This hits especially hard for Project Online (PWA) solutions that:
- Use custom PDPs for project intake or updates
- Include dynamic field logic, conditional formatting, or even alert banners
- Have approval buttons or logic embedded in the UI
Suddenly, your once-beautiful customizations have turned into ghosts.
Don’t Just Patch It
Sure, there’s a tempting solution: “Let’s just re-enable custom scripts in the tenant!”
Big mistake. Microsoft blocked them for a reason: security.
Custom scripts can:
- Introduce cross-site scripting (XSS) risks
- Make your tenant non-compliant
- Get flagged in future audits
This isn’t a bug. It’s a nudge from Microsoft to move to modern solutions.
The Better Path: Power Platform to the Rescue
Rather than trying to duct-tape legacy scripts back into life, use this moment to evolve.
Here’s how you replace script-heavy Project Online customizations with modern Power Platform tools:
Legacy Feature
JS-based PDP logic |
Custom approvals via script |
JavaScript dashboards |
On-change field behavior |
Power Platform Equivalent
Power Apps form with rule-based logic |
Power Automate flow with secure approvals |
Power BI embedded visuals |
Power Apps conditional formatting + validation |
Bonus Benefits of Going Modern
- Secure by design – no script hacking needed
- Mobile and tablet-ready
- Fully audit-friendly – every change is tracked
- Supports role-based access control
- Can trigger automated reminders, escalations, and report packaging
Instead of fragile hacks, you get robust apps.
What EPMA Recommends
At EPMA, we’ve helped clients transition dozens of custom PWA workflows to secure, future-proof Power Platform solutions.
We don’t just “rebuild” what you had. We rethink it:
- How can we make data entry faster?
- How can status reporting be smarter?
- How do we make approvals seamless and trackable?
With Microsoft shifting the foundation, this is your perfect moment to modernize.
Looking Ahead: What’s Next for Project Online?
This isn’t just about script changes. With Microsoft no longer investing in Project Online, it will eventually go away. Some of our clients are now considering what solution to move to next as part of their PPM evolution. EPMA partners with both edison365 and OnePlan to help clients plan and transition with confidence.
Whether you’re ready to modernize with Power Platform or explore your next-generation toolset, we can help.
Let’s Modernize Your Project Online Stack
If your scripts just broke, we feel your pain. But this isn’t the end of functionality.
It’s the start of a smarter, more secure, and more scalable solution.