RolesSetting
Returns all the roles settings.
Select
The provider will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the provider.
- RoleId supports the '=' operator.
For example, the following query is processed server side:
SELECT * FROM RolesSetting SELECT * FROM RolesSetting WHERE RoleId = 1
INSERT
Insert can be executed by specifying the Name and FieldType columns. The columns that are not required can be inserted optionally.
For example:
INSERT INTO RolesSetting (RoleId, SettingKey, Value) VALUES (1, 'deal_default_visibility', '1')
UPDATE
Update can be executed by specifying the RoleId in the WHERE Clause and SettingKey and Value in Body Parameter. The columns that are not read-only can be Updated.
For example:
UPDATE RolesSetting SET Value = '3', SettingKey = 'deal_default_visibility' WHERE RoleId = 1
Columns
Name | Type | ReadOnly | Description |
RoleId [KEY] | Integer | True |
Role Id. |
DealDefaultVisibility | Integer | True |
DealDefaultVisibility. |
LeadDefaultVisibility | Integer | True |
LeadDefaultVisibility. |
OrgDefaultVisibility | Integer | True |
OrgDefaultVisibility. |
PersonDefaultVisibility | Integer | True |
PersonDefaultVisibility. |
ProductDefaultVisibility | Integer | True |
ProductDefaultVisibility. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Value | String |
Possible values for the default_visibility setting depending on the subscription plan. The allowed values are 1, 3, 5, 7. |
SettingKey | String |
SettingKey. The allowed values are deal_default_visibility, lead_default_visibility, org_default_visibility, person_default_visibility, product_default_visibility. |