Example allowing configuration records for a table
On this page
Example allowing configuration records for a table
You can permit other application scopes to create configuration records on application data tables.
You can grant access to the following configuration records with these settings.
<table id=“table_j4n_xjc_br”><thead><tr><th>
Configuration record
</th><th>
Setting required to grant access
</th></tr></thead><tbody><tr><td>
Access controls
</td><td rowspan=“2”>
-
Accessible from set to All application scopes
-
Can read is selected
</td></tr><tr><td>
Business rules
</td></tr><tr><td>
Client scripts
</td><td rowspan=“3”>
-
Accessible from set to All application scopes
-
Can read is selected
-
Allow configuration is selected
</td></tr><tr><td>
Dictionary entry (new field only)
</td></tr><tr><td>
UI actions
</td></tr></tbody> </table>[Omitted image “GrantingAllDesignTimeAccess.png”] Alt text: Granting other application scopes design access permission
The following diagram illustrates the effect of granting other application scopes the ability to create configuration records.
[Omitted image “EffectsOfGrantAllDesignTimeAccess.png”] Alt text: Granting access to configuration records
Parent Topic:Design-time access to application tables
Keep exploring.
Find another answer, or bring this documentation into your own tools.