adding 9.0 security to custom table

 6 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
MC
Advanced Member
Posts: 41
Advanced Member
    we have a custom table within PA, this is for reporting use only.    We get an Addin Error (appears to be security related) for any user using 9.0 security, no problem if user is using LAUA security.

    Also within the Security Admin tool the new table does not appear within PA.

    How do we get this table recognized to 9.0 security ?

    thanks
    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
      You need to have it show up in dbdef in order for it to be a part of LSA.
      Define your table in dbdef, do a dbreorg, and
      you should be set.
      MC
      Advanced Member
      Posts: 41
      Advanced Member
        the table was defined in dbdef and the reorg was done when we defined the table originally. We have no problem updating the table with the new 4GL pgm. Our only issue is this security problem.
        John Henley
        Posts: 3353
          Try doing a server cache refresh and stoplase/startlase.
          Thanks for using the LawsonGuru.com forums!
          John
          Kwane McNeal
          Veteran Member
          Posts: 479
          Veteran Member
            I have a hunch the issue here is either the table was recently defined, and therefore a refresh is needed, as John suggested, although, by recent, I mean within the last hour...
            -OR-
            There are multiple productlines at play, and the table is NOT defined in the one that the LS profile uses as it's master object list (Definition Productline)
            If the LS profile was defined using PLINE1 as it's Definition Productline, and the table is in PLINE2, the table will never show up.

            Your options are to EITHER change the definition productline to the one with ALL the objects, OR, add the object to the definition productline.

            Kwane
            MC
            Advanced Member
            Posts: 41
            Advanced Member
              Table was defined last Tuesday.

              There are multiple PL in that env. Thanks for this one...that may be the issue.
              MC
              Advanced Member
              Posts: 41
              Advanced Member
                Just to let you know this was the issue. Security was tied to an old product line that had been removed.

                Thank you !