Not sure on the multi-line part, but a potential alternative if you are generating the same text string in multiple reports would be to put the complex logic into an XFBR String formula. You'll get the benefit of shortened text description in the cube views at the expense of maintaining the logic in the BR.
Cheers -DB
This is helpful. I will leave the question open for a little longer ... in case anyone is aware of if/how it is possible to have multi-line expressions. The length of some of our expressions seem problematic, and unsustainable.
I realize that I'm using the cubeviews in a fairly unusual way. But I think this issue is one that is eventually encountered by anyone who is working with complex requirements. Perhaps it should be possible to have a small amount of BR logic that is in closer proximity to the cubeview itself... possibly embedded in the cubeview.
I totally agree with db_pdx. In addition to the benefits you are looking for, accessing the properties within a business rule is much easier and cleaner.
My hesitance is related to organization, and deployment. It seems problematic to put logic in another onestream collection, when it is specific to the requirements of a single cubeview.
Also I'm not aware of any CI/CD strategies for pushing an assortment of dependencies thru onestream environments. Adding a new dependency on a business rule is just one additional thing that can get overlooked in the (manual and labor-intensive) steps needed to move a report from dev to test to prod. Let me know if we are overlooking CI/CD features of onestream (automated ones).
