Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Victor Smith]

I have 6-8 dimensions, I want to restrict what users can see as per the login.

So XYZ user can only see ABC dimension.

THanks

——————————
Victor Smith
SCC
——————————

[Lewis Rosenberg]

Easy Security from Mergetool.com can do data level security.

With Standard NAV, you’ll have to play around a bit.
You may need to create a separate permission set for each user, based on what you want to allow them to see using security filters.

——————————
Lewis Rosenberg
IT Manager
Mars Fishcare
Chalfont PA

NAVUG Board of Advisors, Programming
NAVUG Programming Committee
NAVUG Membership Committee
——————————
——————————————-

[Kris Ruyeras]

Depending on the version in NAV, I believe you can do this through Responsibility Center. Creating a responsibility center card and within the card, you can assign the responsibility card with proper dimension values for department, project and even location.

Then assign the user to a responsibility center card from the User Setup.

——————————
Kristoffer Ruyeras
Director of Business Technology
Seattle, WA
——————————
——————————————-

[Ramin Marghi]

Hey Victor,

Lewis is right, MergeTool does offer a FLAD (Field Level, Action and Data) flavour of their Easy Security solution, however do realize that security is something that does require thoughtful setup and ongoing maintenance and review.

Having said that, are you talking about Dimension Codes or Dimension Values that you’re trying to limit?

You can try playing with Security Filters in your Permission Sets. For Dim. Values, you’d put in a Security Filter similar to below:

Which would limit which Dimension Values the user would be able to see/access/etc.

Bear in mind that NAV will take the least restrictive Permissions, so if you have the filter above but have an unfiltered TableData permission for ‘349’ in another Set, that negates this Security Filter.

Now the reason I say try in the above is that Security Filters are sometimes annoying as all get-out — from a data perspective they do their job restricting data, but the way they do it can often times have some strange side-effects (sometimes pages will open, give an error that there’s a filter, and close — sometimes you’ll create a new record and then immediately have an error because of a dependency, and so on).

So play around with the above and see what works/doesn’t work for your build, version, and requirements.

Fun side-note: A couple years ago, I actually spent a whole weekend doing a last-minute “emergency” hack for a client that “needed” to have the “Responsibility Center” security filtering apply to Dimension Values, Service Items, Value Entries, and a whole lot of other data. They didn’t want to purchase a third-party security solution and needed almost immediate turnaround. That weekend I became intimately familiar with how to use the FILTERGROUP function! 😛

——————————
Ramin Marghi , CPA, CGA
NAV Finance Consultant
Catapult
VANCOUVER BC
——————————
——————————————-