Calculate 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
Workflow time format is weird
Hello ! I've noticed that the workflow time stored in the application is having a weird format, for instance : Workflow Time : 022008000 = 2022M5 Workflow Start Time : 2022003000 = 2022M1 Workflow End Time : 2022018000 = 2022M12 The only reason I see for this weird format is on the FX rate table (shown below), as it seems that 2022M1 is in the 4th column (hence 003 if we count column 0), 2022M5 in the 8th column and 2022M12 in the 18th column... --> Is it just a coincidence, or am I assuming correctly the date format ?Cube | Data Access | Data Cell Access Security/Slice Security by U1#Geography
Data Management Access Security Please share your expertise to set up a Cube's Data Cell Access Security / Slice Security to limit data read access as outlined below: Dimension: U1# - Geography Total_Geography = Child 1 + Child 2 = Total / Top North_America = Child 1 / NA International = Child 2 / Int'l Slice Security: Access Level - Read Data by Geography - in a CV and a QV Total_Geo_Data = Read Total data | Read NA data and Read Intl data NA_Data = Read NA data | no data access = International and Total Intl_Data = Read Int'l data | no data access = North America and Total TY for your practical advice - SMEs.
possible to post directly to "translated" without being overwritten? (for USD journal in EUR entity)
hi all, I just want to confirm the tool's approach: If I have a foreign entity (defined as EUR), can I post a journal entry directly to USD (Translated), and it won't be overwritten by the built-in currency translation? (in other words, it won't just overwrite translated with whatever is in local?) Or is there something else I have to do to accomplish a USD journal in a non-USD entity?Actual at other FX rate (PY/Bud/PP) - Currency Neutral - How to view Fcst Scenario at other rate
Two part question. Comparing Actuals as other Rates to remove currency flux We want to take our Actuals and view at PYE, PYP & budget FX rates to take out flux in currency. Is there a feature (outside of creating BR's or Alt Rate types) to do this. We currently have built 3 scenario for the above rates and it works as expected for base level members. Where we run into issues is with converting to Reporting currency at parent members. Ex is converting our EMEA entity (currency - EUR) to USD. The BR seems to store the USD value at the base entity but is converting from EUR to USD at parent level using OS logic (ie current defined rate for Actual scenario). It is not consolidating up the USD value but converting from EUR at parent member. This BR was created almost 6 years ago when we implemented so hoping there is something out-of-the-box now that will do this. I am exploring creating 3 new Rate Types: PY Budget, PYE Actual & PYP Actual. I would copy all the PY rates into these 3 new rate types and then create 3 Actual scenarios, each using these new rates. The big issue is having to copy all the data over from Actuals and then reconsolidating. Hoping there is a better way. Fcst Currency Neutral - Having Fcst at the Budgeted rate We are US company with large % of our business from Europe and the flux in EUR to USD is distorting our review of how we are doing. Looking for a way to see our Fcst how we expect (current process) and at Budget rate. I could copy to new scenario that is set to Budget Rate but we have 12 Fcst scenarios and that would take up alot of resources to copy and consolidate as we would need to do this many times during Fcst process (ie it would not be something we only did once the Fcst was closed but during the process) Would this be a UD8 member and if so, how would it handle Base and Parent level members. Looking for best practice advice on how to handle these two issues.
Quick certification of a Certify Workflow using business rule
Hello everyone, Is it possible using a business rule to make a quick certification for a Certify Workflow? I was abel to complete the Certify Workflow task using business rule but the certification status remains rejected. Thank you in advance for your help. Regards, Antony
OneStream Upgrade
Hi All, For the folks that upgraded to v8 (preferably 8.4 or 8.5), I have few quick questions. How long it took for the whole process? Did you see the performance improvement? Did you require an extensive end-user testing? How was your overall experience with upgrade. Any lessons learned that you can pass on? Thank you in advance for your time. Cheers PMHow to Run Workspace Assembly from a Data Management Step In 6 Easy Steps
This was originally a question.It took a while to figure out, so to save someone else the hours of trial and error, here is the process I use in detail, start to finish, to run a Workspace-based Data Management step in a Workspace Assembly business rule. Here's a How-to step by step: List of abbreviations used below: DM: Data Management WS: Workspace MU: Maintenance Unit BR: Business Rule AS: Assembly 1. Workspace:Set the NameSpace Prefix - this is what gets filled in at runtime for __WSNameSpacePrefix 2. Assemblies: Note these properties 3. Create the Assembly Business Rule:Create an "Extender" business rule, this is done by right clicking files and selecting "Extensibility Rules" Add some test code, to verify correct configuration, such as BRApi.ErrorLog.LogMessage(si, "Hello from the new extender!"then code the way you would any other extender 4. Create The Data Management Group: Create a DataManagement Group in the same workspace that the Assembly that has your business rule is in 5. Create a Data Management Step - Create a DM step in the new DM Group, reference the rule using the pattern: Workspace.{WorkspacePrefix}.{AssemblyName}.{BusinessRuleName} In this case it would be: Workspace.Current.DMTestAS.DMTestStepExtender Note: we could also use 'DMTestWS' instead of 'Current'.We use Current because the DM Step is in the same WS as the Extender Rule. 7. Done! Test the DM Step with run button and check the error log(System Tab -> Logging -> Error Log),for your test code's output.
