Hey Mitchell, currently this is a known limitation of Universal Reports where toggle state cannot be synchronized across other reports in the sheet. In the runtime, we have a concept of a base toggle state and a transient toggle state. The base state is derived from the underlying MDX set expression driving the rows or columns tracked by either TM1Sets or in some cases a raw expression in the hidden parameterized area. Toggling in the row or column axis does not update these underlying expressions in the sheet with the DRILLDOWNMEMBER syntax and only updates the runtime state tracked in memory. The workaround currently is to use the Set Editor (for cases where TM1Set drives the column or rows) to execute the toggles as that will update the base expression. Alternatively, you could preload some MDX into the sheet that is controlled by a dropdown that feeds the raw expression into the hidden parameterized area allowing you to mock up some toggle outcomes ahead of time and use the dropdown to swap between them and synchronize the reports. This is an area that we have been discussing internally to improve and we are still exploring options for a more robust solution that doesn't require the workarounds I described.