How-To – Dynamic Components Without the Clutter: Mastering the New ‘Skip Contains’ Workflow in 3DBI for SketchUp

Jan 22, 2026 | Geen categorie, how-to, how-to-3dbi, how-to-3dbi-sketchup, sketchup | 0 comments

The Concept: Data vs. Context

In this tutorial, you will learn more about our enhanced workflow to face a common dilemma: Modeling Speed vs. Data Hygiene.
We assume you’re already familiar with 3DBI and how to integrate 3D models into that visual. If not, we recommend starting with the following tutorials to gain a solid understanding of the benefits of bringing 3D models into Power BI:

    1. How-To – Custom 3D Power BI visual of a warehouse
    2. How-To – 3D Real Estate dashboard in Power BI
    3. How-to – 3D quantity takeoff dashboard in Power BI

 

The Concept: Data vs. Context

If you use SketchUp for warehouse planning or facility management, you likely face a common dilemma: Modeling Speed vs. Data Hygiene.

To model fast, you want to use Dynamic Components (e.g., a rack that automatically adds shelves when stretched). But to get a clean dashboard in Power BI, you need strict control over which objects have IDs and which do not.

In the latest version of 3DBI for SketchUp (v2.1.2381), we’ve solved this conflict with a new feature called “Skip Contains.”

To understand why this update is important, let’s revisit the ideal 3DBI workflow. A good 3DBI model consists of two types of geometry:

  1. Interactive Data (The “What”): Objects that link to your database (e.g., Pallets, Parcels, Sensors). These must have Instance Names.
  2. Static Context (The “Where”): Objects that serve as visual landmarks (e.g., Racks, Walls, Pillars). These must NOT have Instance Names.

The Power of ID Concatenation

For the Interactive Data, users often create nested hierarchies. For example:

  • Level 1: Row Component (Name: R01)
  • Level 2: Stack Component (Name: 001)
  • Level 3: Pallet Component (Name: 001)

When 3DBI exports this, it joins the names to create a unique ID: R01-001-001. This allows you to model one stack, duplicate it across a row, and simply rename the Row Component to generate hundreds of unique IDs automatically.

The Problem: When Dynamic Components “Pollute” Your IDs

The conflict arises when you try to build the Static Context (the racks) efficiently.

When you use a SketchUp Dynamic Component to generate a row of racks, SketchUp automatically assigns Instance Names to every sub-component it creates to manage them. You will often see names like:

  • Leg_copy

  • Shelf_copy

  • Beam_copy

The Consequence: Because these objects now have Instance Names, 3DBI thinks they are Interactive Data. It exports them with IDs like R01-Shelf#1.

This clutters your Power BI visual with hundreds of useless identifiers that don’t match your database, making it harder to filter and manage your real data.

The Solution: “Skip Contains”

In version 2.1.2381, you no longer have to manually “clean” or explode your Dynamic Components before exporting. We have added a smart filter to the export window.

“Skip Contains” allows you to define a list of substrings (keywords). During the export process, if 3DBI encounters an Instance Name containing one of these keywords, it treats that name as an empty string.

Effectively, all instance names containing the entered substring (“copy” in this case) will be ignored and the object becomes Static Context—visible in Power BI, but without an ID.

Step-by-Step Tutorial

1. Identify the “Polluting” Keywords

In SketchUp, select one of your Dynamic Components (like a rack system). Open the Entity Info or Outliner and look at the names of the nested components.

  • Common keywords SketchUp adds: copy,  #, ...

2. Open the 3DBI Exporter

Go to Extensions > 3DBI > Export. You will see a new input field labeled Skip Contains.

3. Enter Your Keywords

In the text box, enter the substrings you want 3DBI to ignore, separated by commas.

Example: copy

4. Export and Verify

Run the export. 3DBI will now traverse your hierarchy:

  1. It finds your Row (R01) -> Keeps it.
  2. It finds your Pallet (001) -> Keeps it.
  3. It finds a Rack Leg (Leg_copy_1) -> It sees “copy”, ignores the name, and treats it as static geometry.

5. Result in Power BI

Load your .3dbi file into the custom visual.

  • Your Pallets are fully interactive and matched to your data.
  • Your Racks are visible as solid context, but they do not appear in your ID list.

⚠️ Important Best Practice

Be careful not to choose a “Skip” keyword that is also part of your actual identifiers.

Bad Example:

  • You use the word “Row” in your skip list.
  • Your Main ID is named “Row-01”.
  • Result: 3DBI will strip the name from your Row component, breaking the ID concatenation for all pallets inside it.

Pro Tip: Stick to the generic terms SketchUp generates automatically, such as copy or #.

Ready to clean up your exports? Update to v2.1.2381 today and start using Dynamic Components the way they were meant to be used—fast and efficient.

More news

How-To – Getting started with 3DBI-Connected

How-To – Getting started with 3DBI-Connected

3DBI-Connected, an alternative to 3DBI. In this tutorial, you’ll learn how to use our custom 3DBI-Connected visual for Microsoft® Power BI®—a dynamic alternative to the original 3DBI visual.We assume you’re already familiar with 3DBI and how to integrate 3D models...

read more
How To – Live Revit Material Takeoff, in Power BI

How To – Live Revit Material Takeoff, in Power BI

Creating a LIVE Material Takeoff report in Power BI, based on your active Revit model. Starting from version 1.25, RTBI exposes information and quantities of materials from your live Autodesk® Revit® model. To illustratie this, in this tutorial we will use RTBI to...

read more
How-To – Revit Quantity Takeoff report in Power BI

How-To – Revit Quantity Takeoff report in Power BI

Creating a QTO report in Power BI, based on your Revit models. In this tutorial you will learn how to export material takeoff information from Revit and how to import and visualize that data in an interactive Power BI report. The tools needed to achieve this are:...

read more