Forum Discussion

marcobobbiesi's avatar
marcobobbiesi
New Contributor III
3 years ago
Solved

How to call a function in Workspace assemblies?

Hi guys, I coudn't find the proper hint in OneStream. In my dashboards, I'm using several XFBR string rules or Dashboard extender rules. I would like to move some of them to Workspace assemblies, a...
  • hiren's avatar
    hiren
    3 years ago

    Use the following syntax instead of just RuleName,
    Workspace.<WorkspaceName>.<AssembleName>.<RuleName>

    Example- 

     

    XFBR(Workspace.MyWorkspace.MyAssembly.ParamHelper, CleanUsername)

     

  • SStalker's avatar
    SStalker
    3 years ago

     

    Try this:   XFBR(Workspace.Current.MyAssembly.FileName, FunctionName)

hiren's avatar
hiren
New Contributor III
3 years ago

Use the following syntax instead of just RuleName,
Workspace.<WorkspaceName>.<AssembleName>.<RuleName>

Example- 

 

XFBR(Workspace.MyWorkspace.MyAssembly.ParamHelper, CleanUsername)

 

  • SStalker's avatar
    SStalker
    Icon for OneStream Employee rankOneStream Employee
    3 years ago

    If the assembly is inside the same workspace you can use "Workspace.Current".  Note that you do not need to specify the folder name as you cannot have the same file name i different folders.  I'm not sure if it actually blocks you from creating the same file but I'm fairly sure it will fail on compile.

    XFBR(Workspace.Current.MyAssembly.FileName, FunctionName)

    • hiren's avatar
      hiren
      New Contributor III
      3 years ago

      I tried this & thought I would share it here.
      You are right, OS does allow creating same file names across different folders (However, It does block creating duplicate filenames in same folder, may be good to have update in future release :D) but fails during compilation due to namespace conflicts,

  • marcobobbiesi's avatar
    marcobobbiesi
    New Contributor III
    3 years ago

    Hi hiren,

    thanks a lot for the hint. But actually it does not work with me, I've also tried with a simpler case creating a dashboard extender and logging a fixed message just to see whether the rule is call and apparently it's not called at all. I've used Default as workspace, the name of my asembly (XICO_Folder) and the fileName (FolderMgmt), tried with and without .vb and even renaming it without vb) and nothing is fired.

    XFBR(Default.XICO_Folder.FolderMgmt, CleanUsername)

    But I understand this is working on your side, isn't it? is there any pre-requisite, like making the assembly/folder/file visibile? I really can't find documentation or examples about it and such a small thing is driving me crazy.

     

    • hiren's avatar
      hiren
      New Contributor III
      3 years ago

      Sharing few screenshots,

       

       

       

       

       

       

       

       

       



      As SStalker mentioned, if the assembly is in same workspace you can also use Current keyword instead of Workspace Name. 

    • SStalker's avatar
      SStalker
      Icon for OneStream Employee rankOneStream Employee
      3 years ago

       

      Try this:   XFBR(Workspace.Current.MyAssembly.FileName, FunctionName)

      • marcobobbiesi's avatar
        marcobobbiesi
        New Contributor III
        3 years ago

        Guys,

        thank you again, thank you soo much!! This is now working. I've just missed the workspace-dot, stupid me.
        There's one curiosity I have. I did not manage to have it working if I keep the ".vb" extension in the filename. I don't mind about it at all and I'm happy to rename the file without any extension, but am I doing something wrong or do you share the same "issue"?