Announcement
ABCRecent Activity
Dimensions Descriptions via PowerBI connector
Hi, does anyone know how to get the dimension descriptions (other then default) into PowerBI via the OneStream PowerBI Connector? In the OneStream PowerBI Connector, there is the "Get Dimension" part with an "include descriptions" option but it only loads the default description (which is english in our setup). We have also a German culture setting and all descriptions are setup in English and German but I cannot find a possibility to get the German descriptions in PowerBI. Regards MartinMartin_Gebhartl2 hours agoNew Contributor III2Views0likes0CommentsSummary: The remote server returned an error: (502) Bad Gateway
Hello OS Community - We are running into below error while trying to load 1 + million records from SAP via connector business rule. Tried with all the options on Cache Page Size limit, at present it is set as below. We did not have any luck so far. Any recommendations or guidance is much appreciated. Summary: The remote server returned an error: (502) Bad Gateway Thanks.Yaseen8 hours agoNew Contributor III5Views0likes0CommentsLoad to Multiple Scenarios?
Is there a way to load to multiple scenarios from one Workflow? Example, from the below Workflow POV, I want to load to the Actual_PP scenario, but also to the Forecast_PP scenario. I don't want to create a new workflow for forecast because I want to use the values from People Planning that have been calculated for Actual_PP to populate both scenarios. I don't what to load the People Planning register twice and calculate it twice.Brooks10 hours agoNew Contributor III6Views0likes0CommentsForce Excel to store the source number (no scaling) when CV is exported
Hoping someone out there has some ideas on how to make this work... Let's say we have a cube view containing a parameter that allows the user to select a scaling option (millions, thousands or no scaling). The results of the parameter are stored in the CV's default CellFormat. Currently, when the CV is run and exported to Excel; regardless of the scaling selected by the user, the display in Excel is in thousands and Excel stores the entire number (unscaled). For example - if scaling selected is millions: If the number is 345,773,247.11; it displays in the CV as 346, it displays in Excel as 345,773 (but the stored number shown in the formula bar is the correct source value: 345,773,247.11). In other words, regardless of whether user selects thousands, millions or no scaling.... Excel displays as thousands and stores the correct number. If I try to change the Excel format to display in any other way (i.e. millions), it will store the scaled value based on the format and no longer stores the full number. This happens even if I force ExcelUseScale=False. The goal in this exercise is to figure out a way to "display" the exported CV in Excel exactly as it appears in the cube view but still retain the whole number. Using the above example, I would like to see this result: CV Displays 346 Excel Displays 346 Excel stores 345,773,247.11 Is this even possible? I have tried multiple ways to make this work including manual formatting, XFBR, parameters, etc., but I still can't determine the exact combination of formatting options that will result in what I want to see. Would love to hear if anyone has found a way to accomplish this. Thankskmd2 days agoContributor II6Views0likes0CommentsXFGetMemberProperty
Hi Team, How does XFGetMemberProperty works in Excel AddIn? The fields in the formula I have are - MemberNameorScript PropertyName VaryByCubeTypeName VaryByScenarioTypeName VaryByTimeorTimeDimProfileName I want to pull the properties for Text 1 to Text 8 from OneStream Production for Entity, for different Time Periods like Default, 2023, 2024 and 2025. Now the properties I pulled at Default are giving correct result. But when trying to pull at year level like 2023, 2024 and 2025, I am not getting the correct data. It is only showing the data present at Default. But in OneStream Prod, I do have data in 2023, 2024 and 2025 for the Text Tags. In my formula, I was setting VaryByTimeorTimeDimProfileName = "2023". And so on for 2024 and 2025 I am getting the same thing for XFGetMemberPropertyVolatile formula as well. In OneStream my year values are stored in 'Stored Property Value' Can someone please help me here ?pratyaydas3 days agoNew Contributor10Views0likes0CommentsCube View formatting
Have a question regarding Cube view formatting. The client has a column for comments where large commentaries are written point wise which currently are seen as one line. They want to view the same like excel where comments are seen point wise one below another. How can the same be done. Also while exporting the report in excel the wrap text option in the Column cell format under excel only wraps the entire cell but it does not show the comment point wise one below anothernupur6 days agoNew Contributor17Views0likes0CommentsExternal/Internal Gross Profit Calc
Hello, I'm trying to calculate an External and Internal Gross Profit calculation based off a few conditions. To calculate External/Internal GP, I need to allocate the ExtCGSOther group + OpExp using our UD1 MFGResale between External/Internal using an allocation basis of ExtMLBS and IntMLBS (with the exception of account 6123 which is 100% External). I need this calculation to be on a dept by dept basis. I'm not really sure where to start and I tried looking at Golfstream but couldn't find anything that fits what my company is asking me to build. Thanks, WillWillVitale7 days agoContributor9Views0likes0CommentsGovernment Community Cloud v9 Upgrade
OneStream is preparing to release version v9 for our Government Community Cloud customers. This document is a guide to the v9 upgrade process. A v9 upgrade is identified as an upgrade from a pre-v9 version to a v9 version. The designated FedRAMP authorized platform release will be v9 which will be made available to GCC customers later this year. Process Overview: The v9 upgrade has infrastructure and software changes that impact applications and integrations. We will migrate from your existing infrastructure to the new v9 architecture. To prepare our customers for this process, we are providing the pre-requisites for upgrade in advance of the release. See Pre-requisites heading below. In the coming months, GCC customers will be asked to submit a Software Upgrade request in ServiceNow. When the upgrade request is submitted, it will open a Support Case to capture the outputs of the items in the Pre-requisites section below. You will be notified when this is available. Once the pre-requisites are submitted, a OneStream project manager will meet with you to plan a timeline of activities. They will be assigned to the Case, available to meet and assist throughout the process. We will provide a mirrored v9 instance for configuration and testing before your go-live. An application copy is made from your pre-v9 instance to your mirrored v9 instance. The configuration and testing period is timeboxed to 2-3 weeks. The scope of work for the test instance is configuration (for example, SIC setup or business rule compilation updates) and functional testing. We will have you compile your business rules in v9 to determine if there are any new errors resulting from the more stringent .NET 8 compiler. Experts from OneStream will be available via the Case to assist. You should also test all functionality that may not be discovered via business rule compilation. During testing, keep a log of any updates you made to the v9 test instance to remediate issues. When testing is completed, we will schedule your go-live. This is a 4–48-hour process (you will be given a more precise estimate following a database size analysis) of downtime where we copy your live databases to the v9 instances. Weekends and evenings are available. As a final step, you will re-apply the updates discovered during testing, referencing the list you generated. After go-live, your pre-v9 instances are no longer accessible; you will be live in v9. Reference: Plan of Action: GCC v9 Migration Pre-requisites In advance of the v9 release, OneStream will open v9 in the Software Upgrade service catalog. When a v9 Software Upgrade request is submitted, it will open a Case called Cloud Migration Readiness that includes intake forms for the pre-requisite action items described below. We have attempted to put together a comprehensive list of all impacts, but given the customizable nature of OneStream, there may be additional impacts uncovered in testing. We recommend you begin work on these pre-requisite items now. If additional assistance is required before the Cloud Migration Readiness Case can be opened, please open a Case. Please note that these pre-requisites are based on expected approvals for our GCC program. The 3PAO assessment is pending. 1. OneStream IdentityServer Customers upgrading to Platform v9 will be migrated to OneStream’s modern IdentityServer OIS authentication technology. Your identity provider continues to be supported, but a change on our side requires that your IT create or edit (depending on identity provider – see Configuration Guides below) the authentication configuration for each OneStream instance. Pre-requisite steps: Complete any necessary technical reviews by your IT Have your IT configure the new authentication configuration for each of your OneStream instances, referencing the Configuration Guide below per your identity provider and protocol. (See Configuration Process Detail below.) Submit the values gathered in the form of the last page of the Configuration Guide to us via the ‘Authentication’ action item in your v9 Cloud Migration Readiness Case, once available. Configuration details: Provide your IT with the appropriate Configuration Guide, per your protocol and identity provider. Your IT will need site names as input. Your site name is [sitename].onestreamcloud.com, per instance. For DoD customers, your sitename is [sitename].onestream.mil. Additionally, because we are providing you with a duplicated instance for testing, configure [sitename-temp].onestreamcloud.com for each instance. This will ensure you are prepared to access both your testing instances and your final instances after go-live. Example: o Your site names are ‘govcustomer’ and ‘govcustomer-test’. o The sitenames to configure for v9 are ‘govcustomer’, ‘govcustomer-test’, ‘govcustomer-temp’, and ‘govcustomer-test-temp'. We recommend taking a screenshot of each redirect URL and attaching it to Authentication action item submission. This reduces the risk of error and aids troubleshooting. NIPR NET customers will also require a new CSR to be generated for the duplicate Production. This will be provided on your Migration Readiness Case , once available. Configuration Guides: Open ID Connect OIS Entra ID OIS Okta OIS PingFed OIS SAML (with any identity provider) Reference: General documentation Identity and Access Management Guide Note: disregard the section about configuring within OneStream; for our upgrade purposes, we require it in advance of the instance creation. Use the appropriate Configuration Guide below.) For further consultation, open a Conversation on the Cloud Migration Readiness Case. If it is not yet available, open a Case. 2. Smart Integration Connector Smart Integration Connector (SIC) establishes secure connectivity between OneStream Cloud and data sources in your network without a VPN connection. With SIC, you can create and manage network data source integration using OneStream administration interfaces and locally manage database credentials and ancillary files. SIC transition is a requirement for v9 upgrades for several use cases. Use cases for SIC Transition: Customers who are using a Virtual Private Network (VPN) to establish data connectivity between a OneStream cloud instance and a local data source. VPN’s will not be supported with v9 or higher. Customers referencing drivers hosted by OneStream. Drivers being hosted on OneStream servers will not be supported with v9. Examples: ODBC, OLEDB (Oracle), Snowflake, Teradata, Netsuite, SAP, JD Edwards Customers who are utilizing DLL’s. DLL’s being hosted on OneStream servers will not be supported with v9. Pre-requisite steps: Complete any necessary technical reviews by your IT Create the SIC Server (or be ready to deploy it in short order) Install the SIC v9 Local Gateway on the server. You can open a Case to request it securely Submit the ‘Data Connections’ action item in your v9 Cloud Migration Readiness Case, once available. Reference: Smart Integration Connector Guide For further consultation, open a Conversation on the Cloud Migration Readiness Case. If it is not yet available, open a Case. 3. Solutions & Business Rule Changes There are several substantial changes in v9 that impact business rules and Solutions. To prepare for these changes, we recommend that you upgrade to v9 compatible Solutions in advance of migration testing. The process includes multiple application copies from your pre-v9 instance (at initial data load and go-live.) If they are not upgraded in the pre-v9 instance, you will need to upgrade them each time your application is copied to v9. Upgrading in advance reduces risk and complexity. You will compile your business rules in the v9 testing instance to uncover errors, if any. We will have OneStream experts available via the Conversation feature on the Case to assist. Many customers choose to leverage a consultant for this work. Pre-requisite steps: Review Impacted Solutions List, below. Upgrade to any compatible versions in your pre-v9 instance, ahead of the v9 upgrade. Compile your business rules in your pre-v9 instance. We will ask for this on the ‘Customer Specifications’ item of the upgrade Case, when available. The purpose is to rule out any existing errors; we want to focus our efforts on v9. Prepare a list of your Solutions and their current versions. We will ask for this on the ‘Customer Specifications’ item of the upgrade Case, when available. Reference: Impacted Solutions List (note: may need its own community post as right now it’s an Excel doc) Business Rules & Workspace Changes in v8+ For further consultation, open a Conversation on the Cloud Migration Readiness Case. 4. OneStream IP Address Changes The IP addresses of your instance will change with v9. This has potential impacts you can prepare for. We have attempted to put together a comprehensive list of all impacts, but given the customizable nature of OneStream, there may be additional impacts uncovered in testing. Pre-requisite steps: If you have non-VPN web integrations such as API or SFTP, you may need to account for new additional OneStream IP’s in the relevant system. If you can allow your domains in the relevant system instead ([sitename].onestreamcloud.com), we recommend this. Otherwise, we will provide the new Application Gateway IP once the v9 instances are built at the start of the active migration process. If your IT has a strict outbound allow list, for example Cisco Umbrella, ZScaler, or similar products, you may not be able to access the new v9 test instance until they allow it. To prepare for this, review with your IT and ensure for all your site names ([sitename].onestreamcloud.com) that sitename and sitename-temp have been allowed in relevant systems. This will help to ensure that you can access all test instances and live instances. Cloud Note: Integrations using VPN’s are not accounted for here as they will be replaced by Smart Integration Connector. Reference: For further consultation, open a Conversation on the Cloud Migration Readiness Case. If it is not yet available, open a Case. 5. .NET 8 Desktop Runtime .NET is the development platform used by OneStream to build the Platform. Prior to v9, OneStream used versions of .NET referred to as .NET Framework versions. The v7.x Platform release used .NET 4.8. OneStream Platform Release 8.2 or later requires Microsoft .NET 8. Pre-requisite steps: Install .NET 8 Desktop Runtime for all users who will be using the Windows Client*, or prepare to install it in short order https://dotnet.microsoft.com/en-us/download/dotnet/8.0 * v9 provides a browser client for end user functionality. Users working solely with the browser client do not need the .NET Desktop Runtime installed. Reference: For further consultation, open a Conversation on the Cloud Migration Readiness Case. If it is not yet available, open a Case. 6. REST API There is a potential impact to REST API, but the scope has not been determined yet. For now, determine whether you utilize the REST API as your preparedness item. We will share more information when we have it.agoralewski7 days agoCommunity Manager98Views0likes0CommentsCapital planning - Access
Hi, We are using the capital planning module. There is a requirement from client For a few lines, users should not be allowed to change, modify, or delete anything. However, if he adds additional lines, he should be able to edit, add new line or remove. Example: In the budget scenario, data is copied from Actual, and it also has its own budget data. So, for data that comes from Actual, end users should not be allowed to modify or remove. However, for budget data, he should be able to update, change, and remove lines from the Capital Planning Register. Is it possible?Harshada_288 days agoNew Contributor6Views0likes0CommentsBooks - Dashboard Report, preview does not show any data. It is blank.
Hi All, Does anybody have experience working with books which has dashboards as a pdf. In books, I have Report and inside it has dashboard report as a type. Why we cannot add dashboards there. It is only showing components list. Also, I am adding component like data adapter, grid, embedded dashboard but it is not working. In preview section it is not showing any report or output.Harshada_288 days agoNew Contributor7Views0likes0Comments
Getting Started
Learn more about the OneStream Community with the links below.