LBi Report Parameters don't stay set after upgrade

Sort:
You are not authorized to post a reply.
Author
Messages
Duane
Basic Member
Posts: 17
Basic Member
    We did an LBI upgrade, amking copies of the LawsonFS, LawsonRS and LawsonSN SQL Server databases, installed LBI 90110154 which matched our current production LBI version, then upgraded to 9.0.3.2. We also migrated our Lawson Documents and Archive files from the current prod server to our new server. We pointed LBI to our new 9.0.1 Lawson apps product line database. We expected these reports to come up with the parameters we had set in our current production. We can go in and make the correct selection and it will work, but confirming every parameter on every report migrated would not be very practical. Why didn't these parameters stay set as in our current production? Thanks y'all!
    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
      Duane,

      Thats a pretty complicated one as upgrades are very delicate. I assume youve opened a ticket with Lawson? The first thing I could point out is you mentioned you installed 90110154 then upgraded to 9032, I assume you did a step upgrade as youd need to go 901x + latest patches -> 9022 + latest patches -> 903 + latest patches -> 9031 + latest patches -> 9032 + latest patches. If not Id say you might want to start by trying that.
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      Duane
      Basic Member
      Posts: 17
      Basic Member
        hey Matthew, thx for responding ... yes, we went step by step upgrading just like you indicated. We opened a ticket with Lawson but they are shutting us down quickly ... seems like the database and server migration is not supported ... you know, LPS kind of stuff ... I was curious if anyone knew why this may be happening. I'm going through my LBI RS tables now, trying to find where those parameters are set, so wish me luck ...
        Matthew Nye
        Veteran Member
        Posts: 514
        Veteran Member
          Again, its difficult to trouble shoot something like this without being involved but Id put money on the parameters getting lost on the upgrade from 9011 -> 9022. Did you review the report migration log to see if there was anything suspicious? I highly doubt the loss was because of the database copies.
          If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
          You are not authorized to post a reply.