In this video, we explore the VIM table, one of the simplest and lightest tables in the Power BI + VIM data model. While it’s usually just a metadata dump from a single model, it becomes more relevant when merging multiple VIM files—especially in Enterprise workflows. Learn what’s useful, what’s nerdy, and what to ignore.
⏱️ Chapters
00:01 Intro – What is the VIM table?
00:08 Opening the table in Power BI
00:18 Single vs. multiple VIM file setups
00:28 File path (useful for VIM Enterprise users)
00:41 File size, mesh count, and origin (Cloud, IFC, ACC)
00:58 Schema version and revision ID
01:16 Creation and upload dates
01:25 Persistent ID and URL – great for troubleshooting viewer issues
01:51 How to test your download permissions with the file URL
02:00 Access tokens and build info (for IT/troubleshooting)
02:18 What can you do with the VIM table?
02:29 Using it when merging VIMs
02:47 Upcoming: Revit file size reference
03:07 Revit file vs. VIM file size explained
03:15 Wrap-up – a simple table, on to the next one!
📚 What You’ll Learn
✅ What the VIM table contains (and why it’s mostly backend metadata)
✅ When it matters: merging VIM files in Enterprise workflows
✅ How to use the file URL to troubleshoot viewer issues
✅ Why VIM file sizes are way smaller than Revit files
💡 Pro Tip: If you're ever having 3D viewer issues, copy the file URL from the VIM table and try opening it in your browser—it’s the first step in solving storage or access problems.
🌐 More info at https://vimaec.com or the data model docs: https://docs.vimaec.com