It won’t error out, if that user doesn’t have access to the field, the data for that specific field will show up blank in the results.
We want to show the Data, just not have it be editable by the User… But we want it to be editable by the Coder via Customizations / BPMs. So if the User is running a BPM or even a BAQ via Code, we need to see the data if we have to do something with it =) Thats where I dont understand Field Security and its broad cause / effect.
Thank you. The problem we are running into is that our UI is not showing existing field security set in one of our prior versions. I need to figure out why that is. They are visible in the DB table but not in the UI. Our current version is 10.2.200.10.
Hi Tim,
Do you have any pointers on how to achieve the sales user scenario you described?
Thanks in advance
Matt
@Nathan - Any tidbits to share regarding Field Security vs restricting it via an In-Trans Data Directive (with bonus pop-up box on why that specific end user can’t change it!)?
@askulte Something like this?
Trying to release Job?:
Authorized to Release Job?:
UnAuthorized:
User Not Authorized:
1 Like