Question

Planning Best Practices - Versions & Import via API

  • 3 November 2023
  • 3 replies
  • 363 views

Userlevel 1
Badge

Dear Community,

we are currently within our FY24 budgeting process. We have the standard setup with Headcount-App, OpEx-App & Topline App.

Topline-App & HC-App are connected with source systems with daily uploads to have a proper reporting in place. OpEx-App is manual input only.  

To avoid that managers have to incorporate changes (Forecast & Budget 24) in two Versions we use our Forecast Version only. For Budget Versioning we copy a Forecast Version as Budget Version 2024 VX.

We face the challenge, that the imported data will change our Budget Versions VX as well. 

A first idea was to take snapshots of the application and connect the Version of a snapshot into the Core-Reporting, but not sure if this is possible? Or does anyone have any other idea how to lock the data without stopping the imports?

 

BR,

Daniel


3 replies

Userlevel 6
Badge +11

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

Userlevel 1
Badge

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

Userlevel 6
Badge +11

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

Reply