Page 9868 "Security Group Permission Sets"
System Application · System.Security.AccessControl
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
System Application · System.Security.AccessControl · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Access Control |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | Permission Set | Rec."Role ID" |
Specifies a permission set that defines the role. |
| Name | Rec."Role Name" |
Specifies the name of the permission set. | |
| Company | Rec."Company Name" |
Specifies the company name for the permission set. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Add multiple | Add two or more permission sets. |
Procedures
SetGroupCode(GroupCode: Code[20])(internal)
Plus 1 local procedures.
Triggers
OnInsertRecord, OnModifyRecord
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Security Group Permission Sets"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.