How to access Business Rules functions in a file

SRAI
New Contributor III

Hello,

Would you know how I can access all Business Rule functions/ syntax etc in a file or where they are stored in OneStream? Basically, I want to have a list of all functions/ syntax.

SRAI_0-1727745702213.png

Thanks,

Sid

1 ACCEPTED SOLUTION

DoN
New Contributor

No list exist like it seem you want. What you see in the editor is dynamically picked up form the DLL files that the system consist of.

You could use reflection f.ex to go through all the assemblies and write the info to a file, but you would get a lot of info you are most likely not interested in as well.

View solution in original post

5 REPLIES 5

sameburn
Contributor II

Hi @SRAI 

A good starting point might be to download the full client version of the onestream platform you are on from solution exchange. In there will be an api reference document and  .chm file for reference

Similarly, if you go to Marketplace on Solution Exchange there is a solution called Snippet Editor (SNE). This solution also has an xml that you can load via System > Load/Extract that gives you additional snippets than the out of the box ones. But it also enables to save and store your own snippets on your own environment. These are stored in a table called BRSnippets in the Framework database

Hope this helps 

Sam

Hi Sam,

Even i tired to locate the .chm file but could not get it in the client software zip of OneStream, if that is possible for you to share the steps to download that would be really helpful.

Thanks,

Manthan

Hi @manthangandhi 

This is the information available from the API_Overview_Guide (that comes with the full client download).

sameburn_0-1727856872128.png

Thanks

Sam

SRAI
New Contributor III

Hi Sam,

Thanks. Snippets I have in a file. I am wondering where this information is stored. Must be stored somewhere in OneStream.

SRAI_0-1727827547287.png

Documentation won't help as I need list of all OS functions, syntax.

DoN
New Contributor

No list exist like it seem you want. What you see in the editor is dynamically picked up form the DLL files that the system consist of.

You could use reflection f.ex to go through all the assemblies and write the info to a file, but you would get a lot of info you are most likely not interested in as well.