Invalid destination data unit in script
I'm making my first attempt at using the DataBuffer to perform a data copy from a source scenario to a destination scenario. This is being done through a Data Management (DM) step and a Custom Calculate business rule. To keep things simple for this initial version, the input values are hard-coded. Dim dbSource As DataBuffer = api.Data.GetDataBufferUsingFormula("S#Budget:T#2026M7:A#CF101:O#AdjInput:E#ES", DataApiScriptMethodType.Calculate, False) Dim destinationInfo As ExpressionDestinationInfo = api.Data.GetExpressionDestinationInfo("S#Forecast_Q2:T#2026M7:A#CF101:E#ES:O#AdjInput") api.Data.SetDataBuffer(dbSource, destinationInfo,,,,,,,,,,,,,False) Appreciate any inputs to fix this. Thanks
FilterMembers syntax (: vs ,) and base clearing when using GetDataBufferUsingFormula
I’m working on a custom clear process that clears cube data using GetDataBufferUsingFormula() The goal is to dynamically clear data for all base members under the current POV (Entity, UD1-UD4) by expanding any parent members with the .Base suffix. In other words, I want to make sure every dimension in the POV (Entity and UDs alike) is ultimately resolved down to base members before the clear runs. Here’s a simplified idea of what I’m doing: Dim filterString As String = String.Join(":", intersectionParts) Dim fullFilter As String = $"FilterMembers({filterString})" Dim sourceBuffer As DataBuffer = api.Data.GetDataBufferUsingFormula(fullFilter, DataApiScriptMethodType.Calculate, False, destinationInfo) The process builds a FilterMembers() expression dynamically, retrieves the buffer, and sets all cell amounts to zero to perform a clear. However, I’m facing two issues: Some child members aren’t being cleared, even when I use .Base on their parent. I’m not fully sure about the correct syntax for FilterMembers, should the dimensions be separated by colon (:) or by comma (,)? What’s the real difference between the two, especially when dealing with multiple parent members or nested intersections? For example, if I have three parent members in my intersection, I might build something like: FilterMembers(E#MyEntity.Base:U1#ProfitCenter.Base:U2#Location.Base) But it’s unclear whether that colon syntax is correct, or if it should be comma-separated, or another thing is, the use of square bracket...since some base-level data doesn’t seem to clear. Could this be a syntax issue with FilterMembers, or could the problem come from how I’m constructing or passing the intersection into GetDataBufferUsingFormula()? Any clarification or working example for multi-parent .Base expansions with FilterMembers() would be a huge help. Thanks in advance!
Create a parameter to determine the initialization status of each forecast?
Hello everyone, We have set up a monthly forecast that is compared to the budget or actual figures in different cube views. We currently use a parameter to select the forecast month in each cube view, but I would like to remove it and have the latest forecast for the year or year N-1 displayed automatically. I have created an XFBR that retrieves the holding company's turnover for each of the 11 forecasts (January, February, etc., November) and displays the forecast closest to December with a turnover. The problem is that not all users have access to this company, so the BR does not work for them. I could change the BR to add companies to it so that it works for all users, but I find that cumbersome. Is it possible to save a value (X or 1) in a variable when initializing the forecast so that the BR can query this variable based on the Time scenario and thus know which forecast has been initialized? How do you do this in your OS?
account is not translating
Good afternoon, I need help with translating a balance account. We set it up to calculate job to date and load its local currency value, then I wanted to translate it using a job to date rate (also setup as the balance account). The formula attached to the account is for every foreign base entity executes this: api.Data.Calculate("A#JTD_COST:V#YTD:F#EndBalLoad:U8#None:C#USD = RemoveZeros(A#JTD_COST:V#YTD:F#EndBalLoad:U8#None:C#Local * A#JTD_FX_RATE:V#YTD:F#EndBalLoad:U8#None:C#Local)",,,,,"U1#Active.base") The problem is that when I set the original account with Formula Pass then I get an error during the consolidation suggesting the invalid destination data unit in script. When I don't attach any Formula Pass then nothing happens at all. Any suggestions what I miss or how else balance accounts can be translated? Thank you, OlaAbout Security Essentials
This OneStream mini-book offers practical guidance, analogies, and in-depth information to help you design, test, and maintain a robust security model. Whether your company is small, large, public, or private, this book delivers the background and tools to meet your company’s unique security and data requirements. Whether you are a consultant guiding implementations, a developer building solutions, or an administrator managing day-to-day operations, you’ll gain a deep understanding of: What’s possible with OneStream security How to define a Security Model tailored to your company’s needs Extending security with Custom Use Cases (aka Slice Security and more) Reporting off your Security Framework and Application Tables Effective Testing and Maintenance strategies for optimal results From practical advice on security group nesting and naming conventions to detailed information on database tables, API calls, and sample code, this mini-book is your one-stop shop for mastering OneStream security quickly and effectively! To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Chapter 1: Introduction Chapter 2: Framework Chapter 3: Design Chapter 4: Common Roles Chapter 5: Application Security Chapter 6: System Security Chapter 7: Other Security Chapter 8: Security ToolsAbout Foundation Second Edition
Beyond offering a training guide, the focus of this book is on the ‘why’ of design and building an application. While the foundational principles of building a solid, scalable OneStream application have remained largely unchanged, updates contained in this second edition reflect implemented software enhancements, along with the ongoing development of the OneStream landscape. Manage your Implementation with the OneStream methodology Understand Design and Build concepts Build solutions for the Consolidation of financial data, and develop Planning models Create Data Integration solutions that will feed your models Develop Workflows to guide and manage your End-Users Advance your solutions with Rules and Security Take advantage of detailed Data Reporting using tools such as Analytic Blend and Advanced Excel functionality Tune Performance, and optimize your application New content on Workspaces, Smart Integration, Dashboard design, and more. Over 180 updated images. The information contained within this book is relevant to software version 8.4.0. To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Foreword by Tom Shea Introduction [Peter Fugere, updated by Chul Smith] Methodology and the project [Greg Bankston, updated by Greg Bankston] Design and Build [Peter Fugere, updated by Chul Smith] Consolidation [Eric Osmanski, updated by Nick Bolinger] Planning [Jonathan Golembiewski, updated by Jonathan Golembiewski] Data Integration [John Von Allmen, updated by Joakim Kulan] Workflow [Todd Allen, updated by Chul Smith] Rules and Calculations [Nick Kroppe and Chul Smith, updated by Nick Kroppe and Chul Smith] Security [Jody Di Giovanni, updated by Bobby Doyon] Reporting [Jacqui Slone and Chul Smith, updated by Chul Smith] Excel and Spreadsheet Reporting [Nick Blazosky, updated by Nick Blazosky] Analytic Blend [Andy Moore, Sam Richards, and Terry Shea, updated by Chul Smith] Introduction to the Solution Exchange [Shawn Stalker, updated by Shawn Stalker] Performance Tuning [Jeff Jones and Tony Dimitrie, updated by Jeff Jones]About Admin
Whether you are a novice or seasoned administrator, this book examines key concepts to help you understand and manage the financial and data processes of your OneStream application. Written for administrators, this book is filled with technical and functional contexts – whether syntax-related to business rules or general accounting concepts – and dives into practical examples and use cases that provide guidance and insights into commonly encountered themes. By the end of this book, you will have a deep understanding and appreciation of the capabilities that the OneStream platform offers, and have the tools needed to tackle the wide variety of administrative actions that may surface. In this book, we will cover: Components within OneStream, such as application properties, metadata, and workflow Data troubleshooting for missing or off data, whether that is related to integration setup, workflow setup, calculation adjustments in business rules, or more. Translations involving cube and metadata settings, plus the loading and viewing of FX rates. The security framework, and all the nooks and crannies that can be secured within OneStream. Constraining and locking data through systems-level and process-level controls. Considerations – as companies mature – for the updating of new or existing business processes. To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Chapter 1: Introduction Chapter 2: Testing Chapter 3: Application Properties Chapter 4: Metadata Management Chapter 5: Translation Chapter 6: Work the Workflow Chapter 7: Data Troubleshooting Chapter 8: Import and Validation Errors Chapter 9: Constraining and Locking Data Chapter 10: Business Rules Chapter 11: Cube Views Chapter 12: Securing the Pieces Chapter 13: Compliance and Audit Chapter 14: Business as “Usual” IndexAbout Advanced Reporting and Dashboards
Written for administrators, dashboard and report designers, plus end users, and filled with background knowledge and step-by-step guides, this book deep dives into cube views, dashboards, reporting, and highlights the tools and tricks that will take user experiences to a new level. We examine how leveraging the full power of the OneStream Platform will help you move beyond the standard interface, align your end-user experiences with your business and process requirements, promote user adoption through efficiency and ease of use, and truly maximize the value of your OneStream implementation. By the end of this book, you will have a deep understanding of the components that drive the user experience and how and when to use them. You’ll walk away with a plethora of tools and ideas to incorporate into your application to deliver your very own user experience. In this book, we will: Design and build cube views, based on data entry and reporting needs. Discuss the use of cube view extender business rules to expose advanced formatting capabilities. Explore how navigation links and drill to dashboard functionality provide intuitive analysis. Identify the benefits of configuring personalized home pages to ensure user adoption. Create working role-based dashboards inspired by real-world customer requirements. To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Getting Started Keeping The User in Mind The Moving Pieces OnePlace / Out-of-the-Box Basics Cube View Concepts Fundamentals of Cube View Design and Build Cube View Formatting Taking Cube Views to the Next Level Build Your Own Cube View Dashboards Splash Screens and Home Pages Executive Dashboards Administrator Dashboards Dashboards for Budgeting, Planning, and Forecasting What Have We Learned?About Financial Close
OneStream provides a market-leading Intelligent Finance Platform that reduces the complexity of financial operations. It unifies corporate performance management (CPM) processes such as planning, financial close & consolidation, reporting and analytics through a single, extensible solution. The OneStream Financial Close Handbook – written by expert authors – is a practical book for implementors, administrators, and end-users, that dives into the Financial Close with a specific focus on the Account Reconciliations and Transaction Matching solutions. The Account Reconciliations solution is a complete package that plugs into the Financial Close Workflow to leverage data that already resides within the consolidation application, whilst Transaction Matching helps accounting teams automate the collection and matching of large numbers of transactions across multiple sources. With these solutions, OneStream Financial Close delivers the four key pillars of a good reconciliation process: Visibility, Standardization, Efficiency and Control. In this book: Get a better understanding of the Financial Close process, and how OneStream delivers a streamlined, automated solution. Learn how to implement Account Reconciliations through detailed project phases, and accompanying case studies. Get to grips with the administration of Account Reconciliations, including settings, security, and auditing. Deep dive into the Account Reconciliation Solution from the End User’s perspective, including how to prepare a Reconciliation, the sign-off and approval process, and overall reporting and monitoring capabilities. Learn what Transaction Matching is, plus how to build, test, and implement OneStream’s highly automated system. Understand how to administer Transaction Matching through global options, access control, match sets, data sets, rules, and more! To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Chapter 1: Account Reconciliations Overview Chapter 2: Account Reconciliations Administration Chapter 3: Account Reconciliations Implementation Chapter 4: Using Account Reconciliations Chapter 5: Transaction Matching Overview Chapter 6: Transaction Matching Administration Chapter 7: Transaction Matching Implementation Chapter 8: Using Transaction Matching
