Skip to main content
K
KH1
October 14, 2025
Solved

Workflow Leading Practices - Input Data to Parent Entities | Forms?

  • October 14, 2025
  • 2 replies
  • 0 views

Please share your Workflow leading practices to input data to Parent Entities. Thank you.

In addition, please help us with three initial questions below:
 0. Workflow: Parent Input – Forms/O#AdjInput
- Is this Workflow the leading option to input data to Parent Entities?
 -- We prefer not to use Forms/O#Forms by creating alternative Base E#/A# Members as they are massive.

0. If Forms/O#AdjInput is the leading option:
1. Account Dim: Member Properties | Vary By Scenario Type And Time | Adjustment Type
 -- How to massively set A#'s 'Adjustment Type' to 'Data Entry' from the default 'Journals'?
 -- Can we still use Workflow 'Journals' as they are tied to O#AdjInput as the default?

Loading Form Data
2. Form Input Template: Format – CSV v Excel
 -- CSV v Excel: which template format is better and why?
 -- CSV Template: please share a copy here per OS Support.
  -- I couldn't find a Form CSV template in Community, Solution Exchange or Design Guide.

Thank you, SMEs.

Best answer by chul

OneStream allows parent adjustments (as you've mentioned) however you'll need to choose between doing those adjustments via form or journal. This doesn't apply to base entities as you can use both forms and journals on them. You can change the account adjustment type via the grid view, use the metadata builder or extract an xml, carefully modify it and reload it.

Using CSV v Excel for forms... Think about what file type will be easiest for your users to understand and complete. The import to OneStream is identical in both cases. In my experience, the Excel route is far more common than CSV. There's a chapter in the Design & Reference Guide called Loading Form Data that walks through the templates found in the Sample Templates zip file on Solution Exchange as well as instructions on how to create a Form CSV template. 

2 replies

C
chulAnswer
October 15, 2025

OneStream allows parent adjustments (as you've mentioned) however you'll need to choose between doing those adjustments via form or journal. This doesn't apply to base entities as you can use both forms and journals on them. You can change the account adjustment type via the grid view, use the metadata builder or extract an xml, carefully modify it and reload it.

Using CSV v Excel for forms... Think about what file type will be easiest for your users to understand and complete. The import to OneStream is identical in both cases. In my experience, the Excel route is far more common than CSV. There's a chapter in the Design & Reference Guide called Loading Form Data that walks through the templates found in the Sample Templates zip file on Solution Exchange as well as instructions on how to create a Form CSV template. 

H
hfrantz
October 30, 2025

I'll reiterate the prior reply to refer to the Design & Reference Guide for instructions on how to create a Form CSV template. The Community site does not allow attachments except jpg or png:

 

K
KH1Author
October 30, 2025

Thank you for diligently researching and creating Form CSV templates for us, Heidi hfrantz​​.
Would it be helpful to attach your Tabular Form CSV template to the KB linked below? TY.
How to Load to a Parent Level Entity Adjustment via Forms

Terms & ConditionsAccessibility statement