Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
In my company we use security filters applied to tables 23, 25 and 380 since NAV 2009. Recently, we upgraded to NAV 2016 and then to NAV 2017. In NAV 2009 we didn't have any problems. But now, the users are getting error messages whenever they enter a vendor card. The error message says "A security filter has been applied to table Detailed Vendor Ledg. Entry. You cannot access records that are outside of this filter.", and when they click on ok they can continue working. It also appears when they pull a Vendor No. into a purchase order, for example. From what I read, the problem has to do with the calculation of flowfields that use table 380 and it seems that if I change SecurityFiltering Property = Filtered it will work. But I do not know where I can do that for I did not find this property in the table design.
Is it only possible to specify the SecurityFiltering property in C/AL code? If so, where do I add it?
Thanks in advance.
You can use the Access By Permission Property. Check this MSDN article: How to: Remove UI Elements Using the AccessByPermission Property and this one: Access By Permission
Thank you for your reply but in this case the suggested articles do not help. They refer to field or table permissions but my issue is with record-level security filters set to object type = Table Data in permission sets. Example: some users cannot read a vendor and nothing related to that vendor but can read and post to all the other vendors.
The security filters are applied and the users do not see this vendor but, when they enter another vendor card, they get the error message although they hit ok and continue working. I'm sure it has to do on how the flowfields are calculated. It seems as if the security filter is not applied and all the records are selected.
check whether you have applied security filter and as well as given permission to those users ,
Thanks for your reply. I checked all the security filters applied for the users again. The tabledata objects that I set up with security filters are included only in the permission role I created for this purpose. On the others, pre-existing ones, I deleted all permissions to these tables, except on SUPER roles.
We are running NAV 2013 and have the same issue. The SecurityFiltering property is attached to the individual variables which reference the secured tables, as used inside the code of each individual object (Table, Page, Codeunit, etc.). So you would need to:
For example, we use security filters for the G/L Entry table and so all objects we use that reference it, including in Codeunit 90 Purch.-Post, our NAV partner set the the SecurityFiltering property of global variable GLEntry to "Ignored" (for NAV 2013, it may be a different setting for other versions). Here are screenshots.
Yes, I agree with your answer. The issue is the Security Filtering property. I just did not know where to change it.
Gladly, our NAV partner also achieved recently the solution for our case, that can be made both ways: as you showed or changing the code as in:
Business Applications communities