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
OSEmployee1007
OneStream Employee
OneStream EmployeeWorkspace Assembly - Call functions from Finance or Connector business rules
Hi Everyone, has anyone already tried to reference a Workspace Assembly business rule from a Finance or a Connector business rule?
I have a business rule that is packaged to an Assembly in a Worksp...
Assemblies are referenced by importing the namespace
Imports Workspace.__WsNamespacePrefix.__WsAssemblyName.DashboardExtender.TXM_Merger_SolutionHelperThen to use it:
Dim merger_SolutionHelper as new TXM_Merger_SolutionHelper.MainClassAlso, don't use the implementation namespace (TXM_Merger_SolutionHelper) as a variable name. It will cause issues.
Thank you very much RobbSalzmann , I got this to work using a super simple test example. Hope this helps the other possible audience. I am running this on 8.1.
I created a new blank workspace, maintenance unit and assembly:
With a simple file to write something into the error log:
Then I created an Extender rule to execute this using the following properties:
When I run this...
...the message appears as expected 🙂
Assemblies are referenced by importing the namespace
Imports Workspace.__WsNamespacePrefix.__WsAssemblyName.DashboardExtender.TXM_Merger_SolutionHelper
Then to use it:
Dim merger_SolutionHelper as new TXM_Merger_SolutionHelper.MainClassAlso, don't use the implementation namespace (TXM_Merger_SolutionHelper) as a variable name. It will cause issues.
HenningOneStream Employee
OneStream EmployeeThank you very much RobbSalzmann , I got this to work using a super simple test example. Hope this helps the other possible audience. I am running this on 8.1.
I created a new blank workspace, maintenance unit and assembly:
With a simple file to write something into the error log:
Then I created an Extender rule to execute this using the following properties:
When I run this...
...the message appears as expected 🙂
I feel like this would work without the 'Imports' statement since you have it on referenced assemblies and are using the full path when you create the class.
- Henning
Hi Daniel, thank you, good call, you are correct. Not sure what I missed in my earlier testing, probably a typo or so. Now when I re-test without the "Imports" statement, it works just as you say!
