Recent Discussions
Mass modification of a Metadata member attribute
Hi all, Does anyone happen to have the correct syntax for an XML file that modifies a single attribute (member property) and can be uploaded to OneStream without resetting other member properties? A bit of background, I have to add content to the Text7 field of over 3000 members. I tried one version of a XML that only referred to the Text7 property for a single member But when I loaded the xml, some (but not all) of the properties for that member reverted back to original defaults. On the plus side, it DID update the Text 7 field. I'm clearly not defining my XML properly so if anyone has an example of the syntax I can use to update a property without affecting anything else, I would love to see it. I realize I can extract all 3000 members to an XML, but if the Text7 property is not assigned anything, then that property doesn't get included in the extract (otherwise I could simply do a global search/replace): in order to fix this I would have to write a script to run against the contents of the XML and 'add' a line identifying that property and it's contents. I'm hoping there's something more straightforward out there? Fingers crossed. Thanks in advance for any examples you might have.
Environment Monitoring Graph Not Displaying Any Values
Hi everyone, I've been trying to use the Environment Monitoring feature, but for some reason the graph doesn't display any values. The interface loads correctly and I can select different metrics and time ranges, but the chart area stays empty—no lines, no points, nothing. Has anyone experienced this before or have any idea what might be causing it? Any tips on how to troubleshoot or configure it properly would be greatly appreciated. Thanks in advance!Account Attribute: In Use versus Allow Input
Hi all, We have hundreds of historical (no longer valid) accounts sitting in a cube and we are looking at ways of de-cluttering resulting data retrievals to avoid seeing them. But additionally, we want to prevent any accidental loading to these accounts from the source system. For reporting, I know we can populate one of the text fields with some text and then combine that with a Where() clause to filter out these old accounts. But, from a data load perspective, just wondering what the risks / benefits are of utilizing either (or both) of the In Use or Allow Input attributes; to prevent accidental loading of data there. We want to be able to continue to see any historical data for these accounts and be able to drilldown from the parent account and see that data. There are no member formulas associated with these - they are all base accounts. We don't care about the Scenario/Time specificity capability If anyone is using these attributes would very much appreciate any recommendations or hearing what your experience has been (before we go through the effort of testing either of these options). Many thanks, K.
Extensibility report usage
HI, OS has report to verify extensibility. I wanted to know based on exp that what happen when report has an error from technical perspective. We have some ragged hierarchy to full fill our req, but report shows an error so trying to understand if consolidation won't work if that is the case. By they are in UD.
Excel Add-in not working for one user
Dear Users: I had just one user who was not able to get their instance of Excel Add-in 8.4 for various workbooks. However, if the very same workbook was emailed or shared with another users it worked just fine. The main issue is that the user could not "REFRESH" the sheet. Eventually, the Excel add-in started to work. Has anyone experienced this in the past? What was the solution? This is the error message: Description: Object reference not set to an instance of an object. Error Time: 1/17/2025 5:49:51 PM Error Level: Error Tier: AppServer User: xxxxxx Application: OneStream_Prod App Server: vmPRD1int000001 App Server Version: 8.4.0.16413 App Server OS Version: Microsoft Windows NTCalculate values in different scenarios
Hi all, I tried to issue an api.Data:calculate with the following (fake) formula : A#ACCXXX:F:MYFLOW:S#MYSCEN = A#ACC001:F#CHI:S#ACT Of course OS complains because I'm reading from the current Scenario (ACT) but I want to write in a different Scenario that implies a different Data Unit (is it ?) While being in ACT scenario, if I would switch to DataBuffers to write in the destination Scenario (is it?) Could someone point me in the right direction ? I did this, but looks like it doesn't write a **bleep** ! Dim _srcDC As DataCell = api.Data.GetDataCell("A#ACC001:F#CHI:S#ACT") Dim _targetDB As New DataBuffer() Dim _dcNew As DataCell = New DataCell(_srcDC) _dcNew.SetScenario(api, "MYSCEN") ' This WON'T CHANGE <=================== _dcNew.SetAccount(api, "ACCXXX") ' This Change _dcNew.SetFlow(api, "MYFLOW") ' This Change _targetDB.SetCell(si, _dcNew) api.Data.SetDataBuffer(_targetDB, _destinationInfo) In the end, works fine... just doesn't change the Scenario... :-/ What am I doing wrong ? Thanks in advance for your help FabioG
Combo box cell type not working in Excel
I am working on in OneStream V9. I have a workspace cube view with a combo-box cell type. The cube view works fine in the application, but when I open the same cube view using the Excel add-in the combo-box drop down is not active. Any ideas on what I should check? Thanks.Security: Question - Control access to a Scenario
Hi all, I'm hoping someone can see what I'm doing wrong here. First a question: Is Scenario access cube specific? Let's say I have 4 cubes. Currently all 4 cubes give a user access to all Scenarios. If I restrict access to a specific scenario for that user in one cube, does that restriction apply across all cubes? I would assume No - am I wrong? I've been trying to set up restricted scenario access to a group of users in a certain cube. I don't want to touch overall security for the Scenario because there are multiple regions that need access. I've tried to set this up via Slice security (Data Access directly on the Cube) by using a Where clause in the Scenario definition for every group identified in the Data Access (i.e. Planning.Base.Where(Name DoesNotContain X). This doesn't appear to be working. The User themself, has access to multiple cubes and there is no restriction to that scenario in those other cubes. So is it all or nothing? Like do I have to go into the slice security for EVERY cube and restrict access to that scenario in order for this to work? Can't think of another way to resolve this but to modify the Scenario access for every Data Access group in every cube will be a lot of work. Hopefully my question makes sense and thanks in advance for any guidance here.
