Securing Fact Boxes in NAV

  • Securing Fact Boxes in NAV

    Posted by Jesse Reyna on December 7, 2016 at 9:09 am
    • Jesse Reyna

      Member

      December 7, 2016 at 9:09 AM

      We are currently trying to secure some information displayed in a Factbox.  We do not employ any security products like NAV Easy Security at this time but will be in the future.  How could I accomplish this?  I am looking to make the changes in Posted Packages.  Any input would be greatly appreciated.

      ——————————
      Jesse Reyna
      Manager of Information Technology
      Westinghouse Lighting Corporation
      Philadelphia PA
      ——————————

    • Kris Ruyeras

      Member

      December 7, 2016 at 12:26 PM

      Hello Jesse,

      What are you trying to accomplish with the factbox? Are you wanting to prevent them from seeing Posted Packages and/or prevent them from clicking on it?

      ——————————
      Kristoffer Ruyeras
      Director of Business Technology
      Bellegrove Medical Supply
      Redmond, WA
      ————————————————————————-

    • Jesse Reyna

      Member

      December 7, 2016 at 1:43 PM

      Hey Kris,

      There are certain fields that my company is wishing to hide from the Posted Package Shipping Charge FactBox. I was trying to figure if that could be done, so that from a global perspective users that should not be able to can not view them.

      ——————————
      Jesse Reyna
      Manager of Information Technology
      Westinghouse Lighting Corporation
      Philadelphia PA
      ————————————————————————-

    • Kris Ruyeras

      Member

      December 7, 2016 at 4:12 PM

      Hello Jesse,

      If that’s the case and you’re in a NAV version using “RTC”, you should be able to modify the Fact Boxes of what is shown. Of course you’ll have to create profiles and set that profile by disabling Personalization and then assigning users to a specific one. That would be the easiest way to hide those.

      ——————————
      Kristoffer Ruyeras
      Director of Business Technology
      Bellegrove Medical Supply
      Redmond, WA
      ————————————————————————-

    • Ben Baxter

      Member

      December 8, 2016 at 8:07 AM

      Kris’s suggestion is spot on.  You will want to create two similar Profiles, one with the restricted view.

      Then on the restricted Profile, either remove the Fact Box through configuration, and disable personalization, or separate the fields into two Fact Boxes, one for everyone and one with restricted data.  Again configuring the restricted Fact Box off of the restricted Profile and disabling personalization.

      ——————————
      Ben Baxter
      Consultant
      Accent Software, Inc.
      Carmel IN
      ————————————————————————-

    • Matt Traxinger

      Member

      December 8, 2016 at 9:16 AM

      Seems like overkill to disable personalization for the whole system just to hide data from one little factbox. Crippling one of the major features of NAV to do this doesn’t seem like the right approach, although I understand not doing a customization too. This is a customization that can be done in such a way that it would not cause a conflict during an object merge, though. Especially on NAV 2016 and up.

      ——————————
      Matt Traxinger
      NAV Developer
      ArcherPoint Inc.
      San Antonio TX
      ————————————————————————-

    • Jason Wilder

      Member

      December 9, 2016 at 8:09 AM

      If you are in NAV 2016 you can use the AccessByPermission property to hide/show a field based on if they have permission to a certain object.  Seems like this would be the easiest way to go.  Small customization, not a big deal.

      ——————————
      Jason Wilder
      Senior Application Developer
      Stonewall Kitchen
      York ME
      ————————————————————————-

    • Ben Baxter

      Member

      December 9, 2016 at 10:33 AM

      When you disable personalization, you are doing it at the Profile level to only the specific profile.  You are not restricting everyone, just the Users that you do not want to make changes.  Yet another reason to create a new profile for this request is to limit the number of effected Users.

      ——————————
      Ben Baxter
      Consultant
      Accent Software, Inc.
      Carmel IN
      ————————————————————————-

    • Matt Traxinger

      Member

      December 9, 2016 at 10:48 AM

      Exactly, with that approach that user / anyone who uses that profile can no longer use one of the major efficiency features of NAV….all to limit one factbox. It certainly will work, but it doesn’t make sense to me to control permissions through personalization restriction. They are two completely different things.

      ——————————
      Matt Traxinger
      NAV Developer
      ArcherPoint Inc.
      San Antonio TX
      ————————————————————————-

    • Kris Ruyeras

      Member

      December 9, 2016 at 11:11 AM

      Jesse,

      You definitely have options as noted by developers here that would and could meet your requirements. So this will depend on what your expectations will be.

      ——————————
      Kristoffer Ruyeras
      Director of Business Technology
      Bellegrove Medical Supply
      Redmond, WA
      ————————————————————————-

    Jesse Reyna replied 7 years, 4 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Securing Fact Boxes in NAV’ 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!