{"id":1408,"date":"2025-09-17T17:17:14","date_gmt":"2025-09-17T17:17:14","guid":{"rendered":"http:\/\/gogetmuscle.com\/?p=1408"},"modified":"2025-09-17T17:40:24","modified_gmt":"2025-09-17T17:40:24","slug":"reporting-on-single-owner-and-split-deals-in-a-report","status":"publish","type":"post","link":"http:\/\/gogetmuscle.com\/index.php\/2025\/09\/17\/reporting-on-single-owner-and-split-deals-in-a-report\/","title":{"rendered":"Reporting on Single-Owner and Split Deals in a Report"},"content":{"rendered":"
As part of upcoming changes to Deal Splits, HubSpot will no longer create explicit 100% Deal Split records for single-owner deals. <\/SPAN><\/P> \u00a0<\/P> Instead, deals with a single owner will be treated as <\/SPAN>implicitly<\/SPAN><\/I> 100% owned by that user, but will not generate a Deal Split record. This simplifies system behavior and improves performance, but it means that reports built only on the Deal Split object will no longer include single-owner deals.<\/SPAN><\/P> \u00a0<\/P> Reports themselves will not break or disappear, but they will silently exclude any deals that <\/SPAN>do not<\/STRONG> have an explicit split record (which now includes single-owner deals). The underlying data will be incomplete if users do not update their reports to reflect the new model.\u00a0<\/SPAN><\/P> \u00a0<\/P> Replacing <\/SPAN>deal_split owner<\/SPAN> with <\/SPAN>deal_owner<\/SPAN> alone won\u2019t capture both types of deals. If customers want reporting that includes both types, we recommend building a combined report and using a <\/SPAN>custom formula<\/SPAN><\/a>.\u00a0<\/SPAN><\/P> This currently affects deals with one owner (or a 100%, single split). Please note that dashboards may appear incomplete if reports are not updated to reflect the new logic.\u00a0<\/SPAN><\/P> \u00a0<\/P> To keep reporting consistent, we recommend using a custom report or dataset that combines Deals and Deal Splits, and adding a formula field to unify attribution amounts.<\/SPAN><\/P> \u00a0<\/P> Instructions<\/STRONG><\/P>
\n
\n
\n
\n
\n
\n
\n
\n
\nThe workaround<\/SPAN><\/H3>
\n
\n
\n
\n