We are excited to announce a significant improvement to how we deliver Data Warehouse Dump (DWD) datasets which are commonly used to feed VendorPanel system data into PowerBI. To provide more stability and flexibility for your data workflows, we are moving away from "in-place" updates and introducing a formal versioning model.

Why are we making this change?

Previously, any change to a dataset—whether adding a new field or editing an existing one—required a coordinated release. This often felt like a "fire drill," forcing all clients to update their integrations on a specific date, regardless of their own internal priorities.

By moving to a versioned model, we are eliminating these forced migrations. You can now choose to adopt improvements and schema changes on a timeline that works for your team.

How Versioning Works

Moving forward, each update to the DWD will be released as a new, distinct version. Here is what you can expect:

• Parallel Running: New versions will be released in their own versioned folders. The previous version will continue to run alongside the new one.
• Frozen Outgoing Versions: When a new version is released, the outgoing version is "frozen." It will no longer receive updates but will remain available so your existing processes don't break.
• 1-Year Expiry: Every outgoing version will remain active for one year from the date its replacement goes live.
• Self-Tracking & Documentation:
  • Each version folder will contain a README file explicitly stating its expiry date. (The latest version will have no expiry date).
  • Every new version will include a PDF summary documenting exactly what has changed, helping you decide when to prioritize a migration.
• Stay Informed: Every future version release will be accompanied by an Announcekit post. We strongly recommend subscribing to these updates to stay informed about new features and upcoming expiries.

The Net Effect: We can ship improvements more frequently, and you are no longer forced to move on our schedule.

The First Rollout: What You Need to Know

The transition to this new model begins shortly, and the first step looks a little different than future updates.

Current State:

Currently, all CSV files are located in the root folder of your delivery location.

The Change:

With this release, we are introducing a new folder named v1_0. This folder contains the exact same files currently found in your root folder.

Key Details for the Transition:

• No Immediate Action Required: On the day of release, nothing about the existing root folder structure will change. Your current processes will continue to work.
• 3-Month Transition Window: Unlike the standard one-year expiry for future versions, the root folder will only be maintained for three months.
• Your Task: You will need to repoint your data ingestion tools from the root folder to the v1 folder within this three-month window. After this period, the root folder will be retired.

This shorter initial window is a one-time requirement to move everyone onto the new versioning framework, ensuring a consistent and reliable experience for all clients moving forward.

Questions?

If you have questions regarding this transition or how to repoint your integrations to the v1 folder, please reach out to your account representative.