Sprint 2026.6 is a quality and foundations release. We unified case notes behind a single aggregated endpoint, expanded what corporate managers can see and control, and put serious work into making the app more resilient when things go wrong behind the scenes.
Aggregated Case Notes
Case notes used to be scattered across multiple sources, which made the Overview Notes panel harder to reason about and harder to print. We added a single aggregated endpoint that pulls all notes for a case through one shared shape.
What's new:
- Aggregated Endpoint - New
GetCaseNotesAPI returns notes from every source in one call - Shared DTO - All call sites use the same
CaseNoteDtoshape - Overview Notes Rewrite - Overview Notes panel now consumes the aggregated endpoint
- Print Support - Notes can be printed directly from Overview Notes
Corporate Admin Enhancements
Corporate managers got a meaningful bump in what they can see and manage across their organization, along with a small but long-requested flexibility improvement around printed price lists.
- Corporation Branding - The Corporate Manager role can now manage branding for their corporation
- Financial Summary Contract Details - Corporate managers see full contract details on the Financial Summary, via a new reusable
ContractDetailsViewercomponent - Customizable Price List Name - Item types now support a custom Price List Name used as the header on printed retail price lists
Reliability Hardening
A cluster of fixes aimed at how the application behaves when an API call fails, a blob is missing, or a request is denied. The goal: stop turning small backend hiccups into loud user-facing errors or runaway retry loops.
Under the Hood
- Call-not-found cascade fix - Missing calls now return 404 instead of 400,
CurrentCaseIdis preserved on failure, and a newHasCaseLoadErrorflag prevents a retry loop when a case fails to load - MediaService.Download null handling - Download now returns null for missing blobs instead of throwing, and every consuming controller handles the null response gracefully
- ApiService retry safety - Request content is now built via a factory, which prevents
ObjectDisposedExceptionwhen a request is retried - Role-check filters - Role-check filters now return 403 Forbidden instead of 400 Bad Request
- API base address normalization - Trailing-slash normalization on the API base address eliminates a class of 404s
API Versioning Policy
As Solution Center matures, we need a way to evolve the API without breaking existing clients. Sprint 2026.6 introduces a formal versioning policy and the controller scaffolding to support it.
- Policy - Breaking changes must land in a new versioned endpoint; the existing version is never modified in place
- V3 Scaffolding - New versioned controllers live under
Controllers/V3/with[ApiVersion("3.0")] - Non-breaking additions - New optional parameters, new endpoints, and new response fields continue to land in the current version
Bug Fixes
- Fixed Same As Decedent checkbox not unchecking when clearing a shared address
- Fixed Image Grid View when using absolute image URLs
- Restricted Add Organization dialog to Insurance/Trust types so new orgs appear correctly in payment dropdowns
- Filtered inactive disclosures out of the Financials Summary selection screen
- Added an IsTranscript flag on call attachments so transcripts stay out of the Attachments page
- Enforced SAP engraving length limits after sanitization
- Excluded the current funeral home from transfer locations when the active call has no LocationId
- Left-aligned and wrapped the service name column on the Item Pricing page so long names are no longer truncated
- Prefilled the preset deduction amount on the Arranger Add Deduction dialog so configured discounts match the Advisor behavior
- Improved case transfer reliability and correctness
What's Next?
With the foundations in place — aggregated notes, a clear versioning story, and steadier error handling — we can keep pushing on the bigger initiatives without letting the edges fray. Expect continued investment in the family experience and corporate-level tooling in the sprints ahead.
As always, if you run into issues or have feature requests, let us know.
— The Solution Center Dev Team