Cannot get multiple printer definitions to appear in Print Manager - Print Report

 3 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Adam Brown
New Member
Posts: 3
New Member

    I am new to Lawson and I am scheduled to take some training in a few weeks, but for now I am struggling with something that may be easy to resolve, but I am currently stuck and cannot figure it out.  Any help is appreciated.  We are on Lawson v9.

    I set up some printer definitions in LID by using prtdef.  I also set up some printer group definitions using prtgrpdef. Our user wants to see multiple printer definitions to choose from when she goes into the Portal and selects Print Manager, then selects a job from her job list (or from a different user;'s list), then right clicks and chooses Print, then on the Print report window she presses the inquire icon next to the Printer text box.  In that list of printers that appears, she can only see the default printer that I set up for her in LID for her User Profile.  If I sign in to the Portal using our Lawson super-user, I can see the entire list of printers that have been defined defined in prtdef. 

    How can I set it up so the user sees a list of predefined printers in this list?  In a  perfect world, I would be able to specify a printer group definition to identify the list of printer that I would like to appear for the user.

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      Check your environment profile in LSA. Open up the security class that's for the user, check under Printer securable type: Printers.
      CindyW
      Veteran Member
      Posts: 169
      Veteran Member

        We do this in LAUA. On the user's user profile, make sure you add the printer group that contains those printers you want them to access.

        That said, we don't have many users that use this anymore.  Most of them set their printing option to PDF, and then use the Adobe print functionality that lets them select from their list of windows printers.

        Adam Brown
        New Member
        Posts: 3
        New Member
          Thanks for the help, guys. The problem was that we had some missing security classes in our Test environment. Once we added the same ones that we had in Production, everything worked.