Skip to main content
April 10, 2024
Solved

Change the precision of the FxRate

  • April 10, 2024
  • 5 replies
  • 0 views

I am wondering if anyone has changed the precision of the FxRate?  It shouldn't be to hard.  What I am wondering is if changing it would cause other issues ?  

Best answer by JonKunert

Hi Everyone,

I wanted to update everyone. I heard back from support and Yes you can change the number of decimals.  But they discouraged the method I was going to take.  Below is their response in case anyone else needs this info in the future,  

**************OS Support Response**************

Here is the answer from one of our Consultants:

If you submit more than 9 decimals into the exchange rates will not cause any issues. You should test the 9 decimals and see if it resolves their issues.

If the  you decides to create a new table to hold more than 9 digits then you have to check all accounts that are marked as Asset/Liability/Revenue and Expenses are linked to the new table for translating.

The supported way would be to do custom translation, using business rules. At that point you can do anything you want, including pulling rates from custom tables. Please don't modify OneStream application tables directly, if you ever have an issue it will be difficult for us to Support it.

This can also affect KPI depending on the account type. Account type denotes how an account will translate using default logic.

We would still advise that default rates are uploaded, regardless of translation approach.

If you would like to further discuss, we can set a short call with our Remote Consultant.

Hope this helps.

5 replies

April 10, 2024

JonKunert  - Why you want to change it? The FX rate is typically come from external system. example FXLOADER. You can override it but the result of the currency translation will also change. 

JonKunertAuthor
April 10, 2024

we are trying to match what is in our gl.  We want to change the translation otherwise there would be no reason to change it.  I know it’s not a huge difference but it is what the business wants. 

April 11, 2024

I am not sure I understand exactly what the problem/question is. As far as I know FX Rates can be entered with up to 9 decimal places (at least I haven't found anything to suggest otherwise). Are you wanting to change existing FX Rates or just new/future rates? Changing the accuracy of the FX Rates when there is already translated data will obviously have an impact (probably very slight). If it's future rates then there's no problem.

April 11, 2024

Marcus is correct.  In OneStream FXRates are stored as Decimals with 9 digits of precision to the right of the decimal.

April 11, 2024

What are the "old tables" ?


RobbSalzmann_0-1712862392223.png

 

JonKunertAuthorAnswer
April 12, 2024

Hi Everyone,

I wanted to update everyone. I heard back from support and Yes you can change the number of decimals.  But they discouraged the method I was going to take.  Below is their response in case anyone else needs this info in the future,  

**************OS Support Response**************

Here is the answer from one of our Consultants:

If you submit more than 9 decimals into the exchange rates will not cause any issues. You should test the 9 decimals and see if it resolves their issues.

If the  you decides to create a new table to hold more than 9 digits then you have to check all accounts that are marked as Asset/Liability/Revenue and Expenses are linked to the new table for translating.

The supported way would be to do custom translation, using business rules. At that point you can do anything you want, including pulling rates from custom tables. Please don't modify OneStream application tables directly, if you ever have an issue it will be difficult for us to Support it.

This can also affect KPI depending on the account type. Account type denotes how an account will translate using default logic.

We would still advise that default rates are uploaded, regardless of translation approach.

If you would like to further discuss, we can set a short call with our Remote Consultant.

Hope this helps.

April 12, 2024

JonKunert - Thanks for the update and Make Sense!