In some reports, it may be desirable to create a more cohesive visual layout by seamlessly aligning views so they appear on a shared panel. Omniscope views are separate by default, with a few styling overrides, you can achieve a clean, unified appearance - perfect for KPIs, Filters and tightly related views.

This guide walks through the advanced techniques to visually join views using layout tweaks and view-specific styling.

When and why to join views

You may want to join views when:

• Displaying related KPIs side by side.
• Combining one or more views with a Filters view to allow inline control over measures or groupings.
• Presenting multiple time series charts stacked vertically or horizontally with a shared visual context.
• Joining a view with a Content view to include notes, insights or annotations.
• Displaying forecast vs trends, for example a bar/line view of historical values beside a forward looking forecast.
• Showing smaller similar views, such as Dial or Bullet views in a grid.

The example dashboard

To illustrate these techniques, we'll use a fictional call centre dataset. It includes fields such as:

• Date/time of call
• Average call duration
• Call reason
• Whether the call was escalated to a ticket
• Ticket status

The example dashboard displays a mix of KPIs, Line, Pivot and Area and Filter views:

We want to refine the layout by joining certain related views so they appear grouped together visually, so in this example we might want to join:

• The Calls Received and Average Call Duration KPIs
• The Escalation Rate and Open Tickets KPIS
• The Calls Over Time and Call Duration Over Time Line views
• The Call Rason Breakdown and Filters views. In this scenario the Call Reason Breakdown is configured with a measure choice, which can be selected in the Filter view below.

Example: Joining two KPI views

Let's walk through combining the Calls Received and Average Call Duration KPIs in the example dashboard, into what appears to be a single panel.

Before starting, it's important to familiarise ourselves with the report styles. Open the dialog and scroll down to the view styles:

In this report we can see:

• View spacing: 16px
• 1px border
• 10px border corner radius

We need to override these settings in both KPI views. These settings can be found in the Style view options.

For Calls Received (left view):

• Border > Width right: 0px
• Border > Corner radius top-right: 0px
• Border > Corner radius bottom-right: 0px

For Average Call Duration (right view):

• Border > Width left: 0px
• Border > Corner radius top-left: 0px
• Border > Corner radius bottom-left: 0px

At this point we can see we've removed the borders and corners where we want the two views to join, however there is still a gap due to the report spacing setting:

We can remove this gap by setting a negative margin.

For Calls Received (left view): Margin >Right: -9px

For Average Call Duration (right view): Margin > Left: -9px

This creates a slight overlap, minimising any anti-aliasing visual seams.

Repeat for other view groups

We now need to apply the same principles across the other panel pairs described above, tweaking the margins and border/corner styling based on positioning - left/right or top/bottom.

Final polish

There are a few further tweaks we can make on this dashboard now that we've joined these views:

• In the Filters view, uncheck Show device title and toolbar to make the radio buttons the sole focus.
• In the Line views, create a unified title in just the top view, for clarity.
• In the Line views and Area view remove ticks/gridlines to reduce visual clutter.

With these adjustments, you'll have a dashboard where related views appear visually joined, streamlining the user experience and making the report feel more polished and intentional.