Zainab Hannan
17 December 2025
Introduction
In OneStream, rules are the building blocks that automate, calculate, and drive your financial processes. As your application grows in complexity, it often becomes necessary to make rules communicate with each other — allowing one rule to reuse or call logic from another.
This is where Namespace Identifiers come in. They enable you to reference one rule inside another, improving modularity, reusability, and maintainability of your OneStream code.
What Is a Namespace Identifier?
A Namespace Identifier in OneStream is essentially a unique name that groups related business rules together. It acts as a label that helps you organize and access rule functions without causing naming conflicts.
For example, instead of creating multiple rules with similar logic, you can define a namespace and then call specific functions or methods from that namespace wherever needed.
Why Use Namespaces Between Rules?
Namespaces make your OneStream environment:
Modular — You can break large scripts into smaller, reusable components.
Maintainable — Update one rule without affecting all dependent scripts.
Readable — Improves clarity for developers and administrators reviewing rule logic
Common Use Cases
Financial Calculations: Reuse standardized logic for KPIs like margins, growth rates, or allocation percentages.
Workflow Automation: Trigger sequences (like data validation → transformation → consolidation) across multiple rules.
Reporting: Share functions that calculate metrics consistently across dashboards and CubeViews.
Conclusion
Using Namespace Identifiers to reference rules within OneStream is a smart way to keep your code clean, modular, and future-proof. It encourages reusability and consistency, making complex implementations easier to manage.
As OneStream environments scale, small efficiencies like this can greatly improve both developer productivity and system stability.