Member

Line Item Modeling (LIM) upgrade issue: PV9.0.0 SV4.0.0

1 reply
57 views

Hello,

At the client we currently have SV2.0.1 installed for 3 LIM (Workforce, Duration Based & Fixed Term)

While for Fixed Term & Workforce we were able to upgrade to SV4.0.0, for the Duration Based we are not able to and we receive this error:

Error log is also not really telling us anything:

Summary: Error executing Workspace Assembly Service class 'Workspace.LineItemModelingInstaller.LIM_Installer.WsAssemblyFactory'.
Message: Object reference not set to an instance of an object.
Stack Trace:
at Workspace.LineItemModelingInstaller.LIM_Installer.DataAdapters.LIMInstanceDataAdapter.GetInstanceFromSchemaName(String schemaName)
at Workspace.LineItemModelingInstaller.LIM_Installer.Controllers.InstanceManagerController.OpenUpgradeConfirmationDialog(DashboardExtenderArgs args)
at Workspace.LineItemModelingInstaller.LIM_Installer.WsComponentController.GetSelectionChangedTaskResult(SessionInfo si, BRGlobals brGlobals, DashboardWorkspace workspace, DashboardExtenderArgs args)
at Workspace.LineItemModelingInstaller.LIM_Installer.WsComponentService.ProcessComponentSelectionChanged(SessionInfo si, BRGlobals brGlobals, DashboardWorkspace workspace, DashboardExtenderArgs args)

❗Another important aspect is about custom assembly for the Fixed Term Planning, we had a custom assembly which was deleted during upgrade, while there is a warning in the upgrade guide about copying any modified standard objects as copy items, it doesn’t mention anything about deleting custom newly created assemblies or anything else. This is quite a big issue that should be looked into with high priority.

IMPORTANT: Any custom changes to standard dashboards, reports, or business rules should be saved as renamed or copied objects, as future OneStream solution upgrades may overwrite standard objects and remove unsupported customizations.

❗Another Issue with V2.0.1 which I’m not sure if it got fixed with V4.0.0 is that in the register table if a column is having a ‘Control List’ eg. 1 for Yes and 0 for No, you see Yes or No as values but when you filter you have to filter by ‘1’ or ‘0’. Things get even more complicated when you have enums of strings like ‘Buildings’, ‘Lands’, ‘Equipment’, etc and the ids are 0,1,2 - you need to filter by 0,1,2 because if you filter by the display name it doesn’t work. Hope this gets fixed as well.

I am available for any other debugging steps.

Line Item Modeling (LIM)

RobbSalzmann

Employee - Advisor

I know it’s frustrating to lose work. I want to help by addressing the deleted custom assembly for you and anyone else customizing LIM, or any Solution Exchange product:

The guide covers this in Appendix B, Custom Service Factory, which is the supported way to add code to LIM. It says customizations won’t remain in place through an upgrade, and it gives the maintenance step: extract CustomEventHandler_LIM from the Line Item Modeling workspace assemblies before upgrading, then reload it after. The Uninstall section adds that rules and extenders created outside Line Item Modeling and referenced by it are left alone.

For the Fixed Term customization, I’d keep the factory as the guide ships it, with your logic called from its BeforeEvent and AfterEvent methods and living in a separate shareable workspace your team owns. The factory is then a few lines to extract and reload on each upgrade, and your logic is never inside the workspace the installer replaces.

The reason for the separate workspace is ownership. Everything inside the Line Item Modeling workspace belongs to the solution, and the installer is entitled to replace any of it on an upgrade. Everything in a workspace your team creates belongs to you, and the solution lifecycle never touches it. The platform supports this directly: a shareable workspace can be referenced from another workspace, and an assembly can take a dependency on an assembly there. So the factory stays in LIM as the hook the guide provides, and your logic stays out of the path of every future release. The only thing you need to do is back up your change to the factory and restore it after the upgrade.

Here’s a guide that helps map this out: Line Item Modeling (LIM): Example of Setting up my Customizations Outside of LIM’s Workspace(s) for Future Upgrades | Community

Sign up

Login with SSO

Login to the OneStream Community

Login with SSO