Home
|
Forums
|
Contact
|
Search
|
Syndication
[login]
[create account]
Tuesday, November 26, 2024
slxdeveloper.com
Home
Search
Contact us
About slxdeveloper
Syndication
Community
Forums
(NEW!)
Newsletter Archive
Members
Your Profile
Submit Article
General
Administration
(6)
OLE DB Provider
Miscellaneous
(2)
Architect
VBScript
(9)
ActiveX Controls
(6)
How To's
(14)
.NET Extensions
(3)
External
OLE DB Provider
(12)
SLAPI (SlgxApi.dll)
SalesLogix COM
(1)
Web
ASP/ASP.NET
(2)
Web Services
Web Client
Downloads
Samples
(17)
Documentation
(7)
Utilities
(18)
Resources
SalesLogix
(3)
Programming
(1)
11/26/2024 2:24:38 AM
slxdeveloper.com Community Forums
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Administration Forums - General Administration
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the
code of conduct
for posting guidelines.
Forums RSS Feed
Back to Forum List
|
Back to General Administration
|
New Thread
View:
Dynamic
Flat
Tree
Search:
Author
Thread: Field-level Security in SP4 problem?
Jason Buss
Posts: 382
Field-level Security in SP4 problem?
Posted: 01 Jun 06 8:01 AM
buy fluoxetine
buy fluoxetine online no
prescription
fiogf49gjkf0d
I seem to have run into a problem implementing field-level security for custom tables in SLX 6.2 sp4.
I've added a simple 1-to-1 table off of account, making sure that the "Enable Field-Level Security" option is selected. Fields from that table were added to the account detail view. I've also confirmed that the Read Only security profile contains the fields from that table, and are indeed set to read-only. A team was created with a user set to use the Read-Only security profile.
When an Account is created using that team as the owner, that user is not restricted from modifying the values in those fields.
I'm a little bit at a loss. Setting field level security seems to be pretty straight forward. Has any one else run across this? Could I have missed a step somwhere along the line?
[
Reply
][
Quote
]
Timmus Agersea
Posts: 328
Re: Field-level Security in SP4 problem?
Posted: 01 Jun 06 1:21 PM
melatonin
melatonin
fiogf49gjkf0d
You must add a SecCodeID column to your custom table and propagate the Account.SecCodeID value to the child.
Known Issue, Functions as Designed, etc.
Timmus
[
Reply
][
Quote
]
Jason Buss
Posts: 382
Re: Field-level Security in SP4 problem?
Posted: 01 Jun 06 1:33 PM
abilify
abilify
fiogf49gjkf0d
Thanks Timmus! I must have missed that as a known issue. Actaully, it kind of makes sence that slx would need to have to establish record ownership somehow. (although it would be nice if it could do it automatically via accountid)
Oh well... Thanks again!
[
Reply
][
Quote
]
Timmus Agersea
Posts: 328
Re: Field-level Security in SP4 problem?
Posted: 01 Jun 06 2:37 PM
fiogf49gjkf0d
You are welcome, Jason. And no, you did not miss anything as this really isnt considered an "issue" by Sage. I agree with what they have implemented (with your suggestion of inheriting from the parent if not overriden being a very nice addition) but they did not communicate to the community that things changed between 5.x and 6.x nor did they offer up the solution we are discussing now. That is what I have "issue" with.
Timmus
[
Reply
][
Quote
]
Ryan Farley
Posts: 2265
Re: Field-level Security in SP4 problem?
Posted: 02 Jun 06 11:50 AM
fiogf49gjkf0d
Quote:
Originally posted by Timmus Agersea
That is what I have "issue" with.
Oh yeah, don't get me started on this one.
Hehe.
[
Reply
][
Quote
]
Page 1 of 1
You can subscribe to receive a daily forum digest in your
user profile
. View the site
code of conduct
for posting guidelines.
Forum RSS Feed
-
Subscribe to the forum RSS feed to keep on top of the latest forum activity!
slxdeveloper.com is brought to you courtesy of
Ryan Farley
&
Customer FX Corporation
.
This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.
code of conduct
|
page cache (param): 11/26/2024 3:14:43 AM