Project baseline not appearing in Planning console (classic) but not in new Project workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Freshly created baseline renders in Planning Console (Classic) but not in new Project Workspace — clean MS Project re-import, so not an ID sync issue
Environment: SPM Pro, [Zurich — glide-zurich-07-01-2025_patch7a-03-24-2026]
We have a project where the baseline displays correctly in the Classic Planning Console (grey baseline bars + Baseline Start/End/Variance) but does not render at all in the new Project Workspace Gantt.
Important detail: this is NOT a stale-reference situation. The team's process is to delete ALL tasks and ALL baselines, then re-import the MS Project schedule from scratch and create a new baseline. So the baseline is always captured fresh against freshly imported tasks — the task sys_ids and the baseline item references should be fully in sync. That rules out the usual "re-import orphaned the old baseline" explanation.
So the question is: with a clean rebuild, why would a brand-new baseline show in Classic but not in the new Workspace?
What we found while researching: PRB1456826 / KB0964588 ("Planning Console Baseline Errors") describes the baseline failing to render with the browser console error TypeError: Cannot set property 'baseline_start_date' of undefined, caused by records that are NOT Project Tasks/Projects (e.g. Requirements, Decisions) sitting in the Schedule Baselines related list. The workaround is to delete those non-task baseline items. This mechanism wouldn't depend on ID sync at all — a single non-task row in a freshly created baseline could break the Workspace render while Classic tolerates it.
