If you want to keep the import action for snapshoting reason, you might want to filter the source module to export only the forecast. No need to keep the actuals in the target module if you don't use it.
Simply right click on the forecast version and click on "Show", save the view and use it as a source of import. this will import only the forecast.
You can so this via a boolean as well, having a setting module where you select which version should be exported (and using this boolean as a filter), so you can switch to another forecast version without having to change the view.
Hi,
The Actual and Forecast numbers are getting summed and loaded into your target module. To only take forecast numbers,
Option 1: Direct Formula
Use the formula to pull the data, Use SELECT Function
=SOURCE MODULE.VALUE[SELECT: VERSIONS.FORECAST]
Option 2: Import
Step 1: Create a line item in your target module called Staging and use formula to pull data from the source module,
Step 2: Import Value from Staging to Target Line Item.
Regards,
Vignesh M
Thank you Vingesh for the response.
I tried to hide the Versions that i dont need and mapped it with the target Version and it worked.
There was an error rendering this rich post.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…