We've heard feedback from customers wanting to customize the presentation of drivers and their dimensional segment pills on reports. There are three new options for displaying drivers to help you tidy and present your data in a more customizable way:

• Show/Hide Driver Name

• Show/Hide Dimensional Segment pills

• Style Segment pills

See below for what each of these options does. We're excited to see the reports you build!

Pages in Runway are your blank canvas where you can tell your story. We're bringing new capabilities to Pages to make them more yours!

• Images — add visual elements to your pages by uploading images from your computer or embedding them from web links.

• Videos — Bring your content to life with videos. Simply follow the same process as adding images, but choose the "Video" option.

Hide or show block titles — For a cleaner look, you can present charts or tables without titles cluttering the view.

Side-by-Side Blocks — Optimize space and improve layout by placing blocks side-by-side. Just drag and drop a block to the left or right of another to create a sleek, efficient design.

We're rolling out more ways to understand trends in your model. The punchlines:

• Time Comparisons allow comparing to prior periods, displayed as rows.

• Custom Rollups allow aggregating values over intervals, displayed as columns.

• Both options can be found in the Customize menu when you're displaying blocks of drivers.

You can compose the Time Comparisons and Custom Rollups to generate powerful reports and visualization, helping you understand trends and tell compelling stories about your business.

Time Comparisons

New options under "Customize > Compare" allow for quickly spinning up comparisons of your drivers over previous time periods. Use it to quickly generate M/M, Q/Q, or Y/Y comparisons and understand the trendline of your business in a snap.

When selected, each time comparison period is shown as its own row.

Note that this feature displays data over time, from the currently selected scenario. To compare values across scenarios or snapshots, see our Help Center articles on Scenario Comparison and BvA.

Custom Rollups

In addition to comparing versus prior periods, often you might want to roll data up over specific intervals to answer questions like:

• "How much money have we made so far this year?"

• "Did we experience seasonality during any specific quarter?"

With the extension of our Custom Rollups menu, which you can find in "Customize > Rollups", you'll be able to aggregate and present rolled-up data to your heart's desire.

When selected, each custom rollup option is displayed as its own column in the timeseries table. The full set of Custom Rollup options now includes:

• Monthly, Quarterly, and Annual rollups

• Quarter, Half-year, and Year to Date (this sums up to and including the current calendar month)

• Quarter, Half-year, and Year to Last Close (this sums up to and including the month marked as Last Close)

• Trailing three, six, and 12 months (relative to the current calendar month)

If there are additional rollup options that would be valuable for your modeling or presentation needs, drop us a line in Slack or at [email protected].

Combining Time Comparisons and Custom Rollups

With a few clicks, you can combine both tools to create reports that highlight the growth, challenges, and opportunities of your business.

For example, you can quickly generate a quarterly report that compares this year’s performance to last year’s. Here’s how:

• In the Customize menu at top right, select Compare → Time period → 12 months ago.

• Next, select Rollups → Custom rollup → choose both Quarterly and Annually.

We hope these capabilities enable you to flexibly generate reports and involve your collaborators in better understanding the business. Happy modeling!

We're improving time to value in Runway by making interconnected models from your data sources more intuitive to build. This will enable going from integration data to multiple layers of drill-in in Runway in just a few clicks.

What's changing?

Previously, there were specific rules and syntax required to bring integration data into Runway. These rules were inflexible, required intermediate SQL proficiency, and required knowing upfront the granularity you wanted to model at. As a result, bringing integration data has historically been done in partnership with our CX team, making onboarding slower than it needed to be.

The changes we're introducing allow integration data to be brought in as Runway drivers and dimensions right in the app instead of through code, with a configuration you can tweak and manipulate until your data looks like what you want.

This tool also allows you to build multiple linked databases in Runway at the exact level of granularity you need — e.g. being able to see expenses by department, by vendor, and drill between the two.

There's two primary places you'll see these changes reflected:

• On an integration page: you'll now see a "Configure new database" button available once an integration is connected and data is linked. You can ask our team for off-the-shelf queries for our most popular GL integrations like QuickBooks, NetSuite, or Xero, use a Google Sheet link, or queries from any BI tool if your team has them handy!

  

• In a Runway Database: There is a menu at the top of Runway databases where you can view, edit, and add connections to data sources, which can even be other Runway databases. An exploded view of the options and a brief description is below; there's also a video walkthrough linked in our Help Center if you want to see the full end-to-end flow.

  

What does it mean for you?

It is now more simpler and more self-guided to bring integration data into Runway, or to roll up your databases by the categories that matter for your forecasting needs (e.g. departmental summaries) and keep it all in sync.

• You should be able to use SQL queries that your data or BizOps teams have internally, 1:1 with Runway. Data-minded modelers (or your counterparts) will have a much easier time bringing new context into Runway.

• We now recommend that rollups of Runway data be done in databases as opposed to in model pages with "Expand by". See this Loom for an overview.

• If you're working with GL or CRM data, ask our team for our 'starter queries' that should provide a lot of flexibility to bring in integration data and model with it.

We are continuing to invest in additional configuration options for the toolbar described above, as well as providing our off-the-shelf queries directly in the app instead of by request to our CX team. Please share feedback as you have it!

Links to related Help Center articles:

• Integrating and Querying your Data

• Modeling with Data Sources

We’re excited to share an enhancement to Runway that brings greater transparency to how driver errors are surfaced in your models. This update is designed to help you identify and address potential issues more effectively.

What’s changing?

Previously, you might have encountered empty cells in some drivers. These empty cells could indicate a genuine null value or, less obviously, an underlying error in the driver or its input formulas. This lack of clarity could lead to unnoticed errors, potentially resulting in incorrect calculations that are difficult to trace.With our latest update, we’re making these errors more visible by replacing ambiguous empty cells with clear error codes. These error codes will help you quickly identify and resolve issues in your models:

• CIRC: This driver or one of its inputs is attempting to reference itself within the same month.

• DIV/0: This driver or one of its inputs is attempting to divide by 0.

• REF: This driver or one of its inputs references an input that no longer exists.

• TYPE: This driver or one of its inputs is performing an operation on incompatible types.

• FORM: This driver or one of its inputs has a malformed formula.

• ERR: A generic fallback error indicating an issue that doesn’t fit the other categories.

What does this mean for you?

You may start to see these error codes in drivers that you haven’t recently modified. Please don’t be alarmed—this doesn’t indicate a change in the functionality of your models, but rather that Runway is now surfacing pre-existing errors that were previously hidden.

How to debug and resolve those errors?

If you encounter any of these errors, the best way to debug them is to open the details view of the affected driver. First, identify whether the error is originating from the driver in question or propagating from one of its formula inputs. To do this, check the Inputs section to see if the same error is present elsewhere.

Resolving these errors will help ensure your models are accurate and reliable. If you have any questions or feedback, please let us know! We’re here to help you address any issues.

We're back from a team gathering in San Francisco and an official public launch of Runway!

Adding Drivers to your Pages just got easier

Nichole shipped some awesome improvements to make adding the right drivers to add to your Pages a snap. Assembling reports has never been easier.

1. In the "add" menu, drivers are now grouped by their dimensions, so you can find the exact cut of data you're looking for, and even add them all to a block in bulk.

1. The menu for managing a driver's attributes is much more helpful. It used to error if you selected attributes of existing drivers, and there was a nasty state where you couldn't get out of this menu.
   Now, we'll intelligently add the driver you specify to the page you're on, or take you right to them, if they're already there!

Early access to new features

In our next phase of product development, we're investing in a staged rollout approach so new Runway features keep raising the bar in utility and delight. There are a few betas available to enroll in if you're interested in getting your hands on our latest and greatest features. Interested? Drop us a line at [email protected].

• Charts: Improved charts, with more powerful configuration and display options, including several new chart types like Combination, Mixed, and more.

• Plans: A more intuitive experience for editing driver values, and interacting with Plans, including per-cell formatting.

• Integrations: A streamlined way to set up new integration data to be modelable in Runway databases without needing to write complicated SQL.

• Pages: Allowing blocks to be arranged side-by-side on pages to make customizing the layout of your pages even more flexible.

Improvements + Fixes

While we're working on shipping big impact via the betas above, there's a host of quality of life improvements and bugfixes we've shipped. Here's a few that might make your day in Runway a bit brighter:

• We had an brief outage last week; Jon made our error and status pages more accessible in the case that Runway is unavailable so you know what's going on and what to expect.

• Shinjini made it clear when empty Actuals formulae are inheriting from forecast, by showing a lighter version of the inherited formula.

• Our Perf team made Database filtering, sorting, and page loads much faster.

• Seb fixed a bug with the wrong column icons showing up in databases.

• Jon fixed an issue where you were not correctly routed to a newly created database after pressing Create.

• Andrew enabled adding formula filters to find database items without a name.

• Xav made a fix for lookup columns: we removed options that would create a circular dependency.

• Shinjini ensured driver groups added to a page should preserve the source ordering.

• Joe enabled viewing and editing the dimensions a driver has in its detail pane.

• Rishi and Shiv let you reference drivers' values in the future via our Date filters to create forward-looking projections.

• Lars worked some UI magic to make the share menu and the Driver formatting look more consistent and accessible.

• Jon made it so the Customize button is always available on databases.

• Rishi included the current scenario's name in CSV exports so you know which set of projections the export came from.

• Amelia shipped a tooltip to make the guidelines for integrating Google Sheets much clearer.

• Justin fixed a bug where pressing Escape from the "Review and Merge" screen prevented users from getting back into that screen.

That's all for now!

Hey all! Here's the latest edition of updates we're shipping to keep making Runway better:

Selected Cell Summary in Databases

Highly requested, and now live! Fresh off some PTO, Justin shipped a big one on his first day back: selecting value cells in databases will now show summary stats in the bottom-right of the screen, so you can do quick sums and averages without breaking your flow.

Filter Menu Improvement

Xav added a nice quality-of-life fix — the filter menu is now searchable, to help you find the right column to filter by.

Small improvements made along the way:

• Derrick and Andy fixed two styling issues related of text overflow in the formula editor

• Seb and Andrew made updates related to how driver group ordering is handled when adding drivers to a block

• Jon made some fixes that should cause popup menus to cover your context less frequently when adding drivers to a block, and when navigating to a page using a link shared from another platform.

Hey team! Check out the latest updates to keep you pumped and productive. 🚀

Main Scenario Renaming ✏️

• Jon made it so you can now rename the Main Scenario, add an emoji, and description.

Filter Menu Enhancement 🔍

• Xavier added a search field to the attribute dropdown for easier filtering, especially with long dropdown lists.

Stacked Plans Deprecation 🪜

• Elysa deprecated stacked plans (stacked delta impacts). New Delta impacts now replace existing ones on the same cell, just like set impacts. Shoutout to our amazing customers and Nadine helping with the migration!

User Profile Syncing 📸

• Jon improved our user name and profile photo syncing from google.

Plans Display Bug Fix 🐛

• Elysa fixed plans showing up as pills on the timeline even with no impacts. Your timeline is now cleaner and more accurate.

Better Default Landing Page 🛣️

• Jon improved the default landing page for smoother navigation.

That’s it for this week! Enjoy the updates and keep the feedback coming. 🌟

Database granularity is now controlled by the “Segment by” menu

Segmenting your drivers by the right dimensions in Runway is critical to unlocking the power and flexibility of dimensional modeling in Runway. We’ve improved the UI for how this association is defined — you’ll now see a “Segment by” menu in databases. These previously were referred to as “database keys”, and our hope is that this change makes it even clearer how databases work. Shinjini and Lars really worked some magic here!

• You’ll now also see some helpful tooltips when using drivers without segment-by set, or when multiple database rows are linked to the same segment of data.

• Let us know if this helps you use dimensional modeling capabilities more confidently — we’d love to hear your feedback!

• Derrick and Nichole rebuilt the “database timeseries” view. It’s now much faster, and adds support for database drivers. Check it out to see a fully expanded view of every property for every database item.

Assorted performance improvements

Making Runway faster and and more performant continues to be our top priority. This week, we shipped even more improvements to make the app snappy:

• Selasi made an optimization that makes the creation of a draft scenario faster, as well as improved performance on the “Review and Merge” screen.

• Andrew made creating snapshots much faster, and reduced the impact of product deploys on the user experience, so we can continue to ship fast without disrupting the user experience.

• Xav found a fix that should improve load times when navigating to large databases.

Cleaning up your unused drivers is now simpler than ever! 🧹

To ensure your data remains organized and to prevent the use of deprecated drivers, we've added a new "Unused Drivers" page in the left side menu. This page automatically displays any drivers that aren't referenced in any model, database, or page. Simply select the ones you wish to permanently delete, right-click, and choose Delete.

Don't lose your hardcoded Plans when you move Last Close 🔣

To enhance the experience of hardcoding assumptions in Runway, we've adjusted how the Runway computes values for months before Last Close. Here is the new order of precedence:

• If there are hardcoded values that you've manually added for months before Last Close, we display those numbers. If not present;

• We rely on the Actuals Formula for drivers or the integration data for databases connected to an integration. If not present;

• We use any hardcoded Plans that you've set for those months before moving the Last Close month forward. If not present;

• We depend on the Forecast Formula.

Performance boost for multiplayer 🏎️

Have you ever experienced Runway flashing or hanging when another user is making changes in your organization at the same time? This happens because Runway automatically reloads in your browser when changes are made by others, ensuring you always have access to the most up-to-date data. While this is useful, it can also disrupt your workflow. We've made some improvements to ensure that reloading only occurs when necessary, reducing its frequency. This should result in a smoother multiplayer experience in Runway.

Last, but not least, Elysa shipped several Plans bug fixes and UX improvements🐛