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

AndreaF's avatar
AndreaF
Contributor III
2 years ago
Solved

Using a variable in the calculate string formula

Hi, I am in a custom business rule.   I have a calculate formula like the following one, which works fine: api.Data.Calculate("A#Sales1 = A#Sales2 + 50”)   Now let say I want to declare a varia...
Finance
  • JackLacava's avatar
    JackLacava
    2 years ago

    The safest approach is this:

    Api.Data.FormulaVariables.SetDecimalVariable("Growth", 50)

    API.data.Calculate("A#Sales1 = A#Sales2 + $Growth”)

    This approach avoids possible issues with converting numbers to string - when the user executing it has a different Culture, or when decimals get truncated (hence losing precision). There is a blog post discussing it as part of internationalising an application.

RobbSalzmann's avatar
RobbSalzmann
Valued Contributor II
2 years ago

No precision lost in this test comparing parsed interpolated strings to straight Decimals:

 

 

JackLacava's avatar
JackLacava
Icon for OneStream Employee rankOneStream Employee
2 years ago

WriteLine converts to String though, doesn't it...? So if there is truncation, you're just showing it being done twice.

But good for trying things out, I'd be happy to be disproven. Generally speaking, internally we've been told to push formula variables as best practice, since it's definitely the safest option.