Learn about what's new in Line Item Modeling (LIM) SV400 in this new Tech Talks After Hours!

Join Gary Malone and Tom Linton as they examine Line Item Modeling (LIM) SV400 release and share some helpful tips, techniques and implementation strategies! 

Line Item Modeling (LIM) — Solution Version SV400

• What is this update? This episode is part of an ongoing planning series tracking Line Item Modeling (LIM) as it evolves based on community feedback. This installment focuses on solution version SV400, the latest incremental release, covering performance enhancements, bug fixes, and implementer tips from Gary Malone, a OneStream solution expert.
• Where to find release notes You can navigate directly from the solution's help desk to its release notes, which are cumulative — showing not just SV400's changes but the full history of enhancements and fixes across versions. This is useful both for your own awareness and for conversations with clients about whether it's the right time to upgrade.
• Background resources LIM has a large library of existing materials: a prior Tech Talks Live episode on migrating from People Planning (legacy) to LIM, content on Workforce Planning Express (a bolt-on to LIM), and a full set of on-demand courses searchable in Navigator under "LIM."
• Granular, role-based security SV400 (building on recent versions) addresses a common pain point: OneStream admins and end users with broad application-level access could unintentionally see sensitive employee data (salaries, names) they shouldn't. LIM now supports role-based security within the solution itself, letting you restrict visibility of sensitive register fields (like employee name) independently from calculation results, and even govern access by other register fields (e.g., department).
• A practical security technique To avoid users inheriting overly broad visibility through nested platform security groups, Gary recommends creating solution-specific entities and security groups (using a consistent prefix) that mirror your real entities. This keeps LIM access auditable and easy to maintain, with a parent "admin" group for roles like HR that need full visibility, while everyone else is scoped narrowly. The guidance: build security like "a warm hug" — start tight and loosen only as needed, since it's easier to grant access later than claw it back.
• Cube drivers now live in the solution Previously, cube driver logic lived in custom business rules, which had to be manually carved out during upgrades or migrations. In SV400, cube drivers are first-class objects within the solution, called via substitution variables instead of business rule functions — simplifying setup and making them migrate automatically with the solution.
• Building cube drivers faster The normal workflow is: build a cube view showing the target number, right-click for the Cell POV, and paste it directly into the cube driver setup — the solution auto-populates dimensionality so you don't have to hand-code intersections. Fields can be hardcoded or made dynamic (e.g., tied to a register field, a substitution variable for entity, or a parent time period that automatically resolves to base-level months). Gary also shares a power-user shortcut: editing the Cell POV string directly to swap in variables and parsing out the account member lets you rapidly generate POVs for many cube drivers at once, reducing manual steps and typo risk — useful when building dozens of drivers rather than just a few.
• Known migration issue with cube drivers Because cube driver data is stored by internal member ID (not member name), migrating a dev-to-prod JSON configuration can produce "invalid member" errors if member IDs fall out of sync — typically after new solution-specific metadata is added post-app-copy. Plan-tab invalid members can usually be fixed via a pick list in the UI; cube driver invalid members currently require manually resetting the account/scenario dimension in each affected driver.
• Free remediation support for migration issues If you hit this issue, OneStream's Customer Support/Remote Consulting (CSCR) team can resolve it at no cost — open a ServiceNow case, and they'll collect source/target objects and return a remapped JSON, typically same-day.
• Upgrading safely Gary recommends a safe upgrade pattern: extract the solution's configuration file, stand up a new instance using the installer, load the JSON there, and validate before cutting over — rather than upgrading in place. This protects your existing environment while you confirm the new version works as expected.
• Key Takeaway: SV400 strengthens LIM's security model with solution-specific, role-based access controls and moves cube drivers natively into the solution for easier maintenance and migration. Gary's field-tested techniques — prefixed security groups, Cell POV shortcuts for bulk cube driver creation, and a safe instance-based upgrade path — give implementers practical ways to avoid common pitfalls. Upgrading from earlier LIM versions to SV400 is recommended, and OneStream will provide free support for any migration-related member ID issues that arise.

To receive OnePoints for watching this Tech Talk video, please visit the link below:

Navigator link: Tech Talks After Hours: Line Item Modeling (LIM) SV400