The problem
We manage a workspace with ~340 engineering projects, each in its own folder with a Master Data sheet. We use automated scripts (Python + SmartSheet API) to maintain
phase-based reports that group these sheets dynamically — e.g. all projects in "Execution" phase in one report, all in "Backlog" in another.
Today, the only way to change which sheets a report references is to delete the report and recreate it. This causes two problems:
- Broken bookmarks and favorites. Every time a report is recreated, the report ID changes. All users who favorited the report or bookmarked its URL lose access until they re-favorite
the new one. For reports shared across a 20-person team this creates weekly friction. - 100-sheet cap on POST /reports. The sourceSheets array in POST /reports is limited to 100 sheets. My workspace has ~340 Master Data sheets, so I'm forced to split what should be a
single report into multiple parts (e.g. "Report - Execution Phase 1/2" and "Phase 2/2"), making the user experience worse and doubling maintenance.
What I'm requesting
- A PUT /reports/{reportId} endpoint (or equivalent) that allows updating the sourceSheets array on an existing report without changing its ID. This would let automation keep reports
in sync with the workspace without breaking links. - Raise or remove the 100-sheet limit on the sourceSheets array for both POST and the requested PUT. The UI already supports reports spanning hundreds of sheets (manually added). The
API should match.
Impact
These two changes would allow teams with large, dynamic workspaces to fully automate report management — something that's currently only possible with manual workarounds that scale
poorly. My team's workaround (delete + recreate on a daily schedule) generates 4 report rebuilds per day, breaking favorites each time, and splits reports artificially due to the cap.
Workaround today: Delete and recreate reports via API on a schedule; split into multiple reports to stay under 100 sheets; re-communicate new URLs to team after each rebuild.
Ref: Support Case# 09746242 (confirmed not currently supported, 2026-07-28)