Skip to main content
M
maxpaul
Member
July 23, 2026

OneStream 9.3.1 Upgrade Feedback - .NET 10 Considerations

  • July 23, 2026
  • 10 replies
  • 150 views

We're currently evaluating the upgrade to OneStream 9.3.1 and noticed that this release requires a move to .NET 10, which appears to be a more significant prerequisite compared to previous 9.x upgrades.

For those of you who have already completed or are planning the upgrade, I'd appreciate hearing about your experience and any lessons learned.

Questions for the Community

1. Infrastructure & Compatibility

  • Did the .NET 10 requirement introduce any challenges in your environment?
  • Were there any compatibility issues with existing servers, middleware, integrations, or third-party software?

2. Upgrade Effort

  • How much additional effort did the .NET 10 migration add to the overall upgrade?
  • Was the .NET upgrade straightforward, or did you encounter unexpected issues during installation or testing?
  • Were any rollback plans needed? any issues occur and popup related?

3. Performance

  • Have you observed any performance improvements or regressions after moving to 9.3.1 and .NET 10?
  • Were there any noticeable impacts to application startup times, data loads, cube processing, or workflow execution?

4. Lessons Learned

  • If you could do the upgrade again, what would you do differently?
  • Are there any "gotchas" or recommendations you would share with others planning their 9.3.1 upgrade?

 

Thank you!

10 replies

M
maxpaulAuthor
Member
July 23, 2026

Also on the topic of .net shifting towards SSH sftp.

    J
    Sage
    JackLacavaSage
    Sage
    July 28, 2026

    The .net 10 migration effort should be fairly trivial, if coming from another 9.x release. Please don’t let that hold you back - Microsoft is retiring support for .Net 8 in November of this year.

      DavidSebenaler
      DavidSebenaler
      Member
      July 28, 2026

      You can download the runtime library/hosting bundle from here: https://dotnet.microsoft.com/en-us/download/dotnet/10.0. I’d encourage coordinating centralized distribution with your IT org via Intune. 

      D
      db_pdx
      Contributor
      July 28, 2026

      We went from v8.4 to v9.3.1, here is some feedback.

      Infrastructure

      • .NET10 was generally easy. Our end-user devices team put the .NET10 Desktop Runtime into Company Portal (part of Intune) which automatically deployed the runtime dependency to end users
      • The business rule integration update from WinSCP to Renci.SshNet was done by the OneStream support team and was also ok.
      • We ran into issues with our REST API integrations timing out with ‘Bad Gateway’ errors. It took a number of tickets and troubleshooting with OneStream support to fix.
        • To make a long-story short: there was a poorly communicated change that turns ON timeouts with a low default value. (edit: reference Call State for Long Running Requests)
        • Our integrations were using the old API endpoints (v5.2.0) that do not support polling causing them to always fail with the ‘502 Bad Gateway’
        • We had to switch our integrations to the API endpoints that support polling (v7.2.0)

      Upgrade Effort

      • .NET10 for end-user devices is straightforward.
      • It’s worth mentioning that end-users cannot have v8 and v9 Excel-Addins at the same time.  This made testing a bit tricky as folks could only have one version of the add-in. This limited the amount of feedback we received on the add-in which plays into our issue noted below in performance.
      • We ran into some issues with outdated versions of Marketplace solutions that was discovered during testing.  This required that we update versions of the solutions to make them compatible with v9.

      Performance

      • SIGNIFICANT REGRESSSIONS with the Excel Add-In. Feedback from across all our divisions is the same:
        • Excel is crashing more frequently
        • Excel based reports that previously refreshed in seconds/minutes now take longer (we’ve heard >30 minutes in some instances) and Excel is unusable in the interim.
          • XfGetCell reports are the ones experiencing the worst performance
        • The add-in frequently locks up with ‘waiting for another application to complete an OLE action’ (Bug# PF8-3618)
      • Feedback from users is that the desktop/native client feels more responsive and loads faster

      Lessons Learned

      • It feels likely that we will not upgrade to the leading edge again

      (edits: typos, +added a link to the REST API documentation)

        mleary302
        mleary302
        Member
        July 28, 2026

        Great information, we also have had issues with REST API call timeouts (not fully live yet so working through this before our initial go live in October).  One question regarding the Excel Add-in, there was a newer version that was just released with the 9.3.1 hot fix (presuming so since you went directly to 9.3.1), have you used that version of the Add-in to attempt to resolve the crashing issues?

        We have not moved our version of the add-in to 9.3.1 yet (still on 9.3) and curious if it will make any difference?

        D
        db_pdx
        Contributor
        July 28, 2026

        Oooh, our addin is still 9.3.0.18429. Sounds like something to explore further. Thanks!

          Terms & ConditionsAccessibility statement