Hi jgaptelligence,
If I understood your explanation correctly, there seems to be 2 different issues with that set up.
Issue 1:
Assembly Business Rules and Assembly Services are two different things and work in different ways.
One of the main differences is that Assembly Services use Service Factory and specific Service type assembly files (referenced by the Service Factory). Assembly BR use the Business Rule Assembly file types and must be do not work with Service Factory.
The syntax to call Assembly Services and Assembly BRs from a button is also different.
For example, when using Assembly Services, you don't reference the rule or funcion name, only the Service Factory that will route it to the right rule/logic depending on the action (e.g.: WsAssemblyServiceType.Component in case of a push of a button)
In summary, the problem seems to be that you are trying to use a ServiceFactory but using the Assembly Business Rule syntax.
Issue 2:
When using Assembly Services the objects can only access the Service factory defined in their own MU level or at the Workspace level.
It seems that you created a button in MU1 (i.e.: Reconciliation Manager) that is trying to launch the service factory assigned to MU2 (i.e.: MyMU). That won't work.
Relevant info:
You might find the Assemblies webinar and the Service Factory blog interesting:
Workspaces & Assemblies | OneStream Community
Service Factory: Service Factory in Practice | OneStream Community
Hi FredLucas,
I appreciate the information.
However, something still isn't clicking for me.
Based on what you said in Issue 2 - I don't see how this call would work:
Because that follows the syntax of Workspace.WsNamespacePrefix.AssemblyName - and the Integration assembly is only within it's own Integration maintenance unit in the OFC workspace.
So using your reasoning, this 8.4 out of the box call shouldn't work since this is a button inside of the Reconciliation Manager MU that is trying to launch something inside of the Integration MU.
Let me know your thoughts.
Thanks!
