Forum Discussion
RobbSalzmann
4 days agoValued Contributor II
In my experience, It's not necessary to create a "String service" XFBR then reference it by calling a Service Factory. I don't know why OS chose to this complicated design approach for assembly-based XFBR.
Simplified Approach:
Here's how to do it in a way that calls the XFBR directly, no service, no implementing an undocumented interface with the version hardcoded into its name (IWasXFBRStringV800), no calling a factory to build and return that service:
- Right click the assembly directory where you want to create your XFBR.
- Select Add File.
- elect Dashboard String Function Business Rule assembly file
- The file name becomes the name of the assembly file and the rightmost element of the Assembly file's namespace.
- In your component or cube view, reference the assembly XFBR as follows:
- XFBR(Workspace.{WorkspaceName}.{AssemblyName}.{AssemblyFileName}, {FunctionName}, paramName=value)
- XFBR(Workspace.{WorkspaceName}.{AssemblyName}.{AssemblyFileName}, {FunctionName}, paramName=value)
Related Content
- 4 years ago
- 2 years ago
- 6 months ago
- 9 months ago