The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
denisefockler
1 year agoContributor
Public Overloads Function GetCalculatedFxRate... is obsolete
Is someone able to assist me with an alternative method for GetCalculatedFxRate on line 14 of the code below? We just upgraded to 8.5.1 and this is no longer being supported. In 8.2.3 it was still ...
- 1 year ago
Not just obsolete but also slightly changed; we observed different output in certain situations which is the issue mentioned below. GetFXRate is supposed to replace GetCalculatedFXRate and GetStoredFXRate.
I would just forget the workaround mentioned and use GetFXRate since it seems to be the way forward.
DanielWillis
1 year agoValued Contributor
Not just obsolete but also slightly changed; we observed different output in certain situations which is the issue mentioned below. GetFXRate is supposed to replace GetCalculatedFXRate and GetStoredFXRate.
I would just forget the workaround mentioned and use GetFXRate since it seems to be the way forward.
denisefockler
1 year agoContributor
Thank you. I did get a response back from OneStream on the case I opened. In addition to what you have mentioned, they provided me the attached document with more extensive examples of how to correct. I have it working now. I am still confused on why this was not mentioned in the 8.5 release notes. We review release notes a few months prior to the upgrade. In your experience is there another resource available from OneStream that would list defects for a given release that I should be reviewing in addition to release notes? I compile all BRs and Formulas before and after the upgrade but had no way of catching this issue because the compile just showed a warning.
- DanielWillis1 year agoValued Contributor
I have the same pdf from support and I don't understand why it isn't provided either. I didn't share it because OneStream hadn't made the doc public for whatever reason and I didn't want to tread on any toes. I echoed your thoughts on my support ticket at the time. There was a decent amount of time spent investigating / responding to this.
Related Content
- 1 year ago
- 4 years ago
- 2 years ago