Hello,

why would the data import change your budget ?

Typically the loads are made so as to not disturb “past” versions. Would love to hear what import you do and how they are so we can help you

Hi Nathan,

we import Subscriptions & Charges from Netsuite (Dimension lists updating the whole dataset)

With Subscriptions we calculate the length of contracts and define the type of the ARR-Bridge (New Logo, Upsell, Downsell, Cross-Sell, Churn, etc.), with the (subscription) charges  the ARR is calculated. As there are non-standard contracts with complex billing cycles in place there is a need to adjust some ARRs. That was the reason I didn’t import with a load date/month as i had to do those changes every time.

BR,

Daniel

So you effectively recast the past with every load potentially ?

Firstly you should definitely do snapshots. they are full copy our the app that you can use to compare against or actually open and explore. 

However there’s some limitations on how you can use them, so typically, it is not the only thing we do.

Given what you tell us here, my suggestion is: you have metric(s) that aggregates from your TL

You can create copies of these metric(s) and do a “manual” (or a pigment to pigment import) snapshot of your values for your “finished” versions.

Then in the final metric, you can do a IF statement, bringing the LIVE values from the TL or the archived metric(s) depending on the version type.

That won’t save the TL (but you have the snapshot for that) but will make sure your values are frozen