User Security Question

  • User Security Question

    Posted by MARY MALLAZZO on July 31, 2019 at 11:46 am
    • Mary Mallazzo

      Member

      July 31, 2019 at 11:46 AM

      Hello
      Does anyone know if it is possible to create a security task/roll that will allow a user to maintain a vendor, but create one?

      Thank you

      ——————————
      Mary Mallazzo
      Fromkin Brothers
      Edison NJ
      ——————————

    • Mark LeRette

      Member

      July 31, 2019 at 3:18 PM

      I’m pretty sure you can, although you’ll need to set up Field level Security as well. Depending on what other functions you want this person to have with relation to Vendors, you would make a copy of task CARD_0301 and strip out unneeded functions while keeping Vendor Maintenance.
      Then you could create a Field Level Security item to remove access to any fields/buttons on the Vendor Maintenance form you don’t want the person to update/have access to.

      ——————————
      Mark LeRette
      Application System Analyst II
      Muscatine Power and Water
      Muscatine IA
      ——————————
      ——————————————-

    • Beat Bucher

      Member

      July 31, 2019 at 7:45 PM

      I’m in with here..
      As soon as you give access to any user to any “Maintenance” form in GP, they will have the same ability to create / update / delete a record.. unless you put in some limitation like it was mentioned with Field Level Security.. and even that I’d have to find a creative way of doing it by probably putting some passwords on key fields or buttons.
      GP Power Tools has a developer module with triggers that you could code to control the Vendor Maintenance form, and based on the user account that is trying to access the form, forbid the creation of new vendor cards.?

      ——————————
      Beat Bucher
      Business Analyst, Dynamics GP SME
      Montreal QC/Canada
      @GP_Beat http://www.gp-geek.com
      Montreal QC GPUG Chapter Leader
      MBS MVP (2015-2018)
      All-Star 2013
      ——————————
      ——————————————-

    • David Musgrave

      Member

      August 1, 2019 at 2:46 AM

      is correct. A simple GP Power Tools trigger on the Vendor ID field can be used to stop the entry of a Vendor ID that does not already exist for selected users (or for everyone, but selected users).

      I don’t think field level security can do what is needed. When I originally wrote Field Level Security (as Omni Field Security), it had scripting capabilities, but these were removed when Microsoft purchased the module from me.

      Regards

      David??

      ——————————
      David Musgrave MVP, GPUG All-Star

      Managing Director
      Winthrop Development Consultants

      Perth, Western Australia

      http://www.winthropdc.com
      ——————————
      ——————————————-

    • Jo deRuiter

      Member

      July 31, 2019 at 3:41 PM

      Hi

      I, honestly, do not think so, but you can test out the two operations below by creating a new security task and assigning one of them to it

      ?

      ——————————

      ——————————
      ——————————————-

    MARY MALLAZZO replied 6 years, 10 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘User Security Question’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!