@@ -57,7 +61,7 @@ A sample output would be like the following
For entities other than the Contact Entity you can use an alternate notation to the `custom_n` to specify the custom fields you wish to return. You can use `custom_group_name:custom_field_name`. Read carefully the documentation and parameters in `CustomValue.php` for more alternatives and details.
!!!note
When retrieving custom data for contact entity, it will only return one value in the case of a multiple custom group set whereas for other entites e.g. Address, or using the CustomValue.get API you will get all custom data records that relate to the relevant entity
!!!note
When retrieving custom data for contact entity, it will only return one value in the case of a multiple custom group set whereas for other entities (e.g. Address, or using the `CustomValue.get` API) you will get all custom data records that relate to the relevant entity
The CustomValue Entity implicitly deteremines what the `entity_table` variable should be when it is not supplied. If developers are finding that the implicity is not working out exactly then developers should spcifiy the `entity_table` key.
The CustomValue Entity implicitly determines what the `entity_table` variable should be when it is not supplied. If you find that the implicitly is not working out exactly, then specify the `entity_table` key.
There are many API Options accepted by the CiviCRM API. These options allow the developer to add in more paramaters to the resulting Query that is run against the databasae. E.g. Limit, Sort. You can explore these options using the the [API Explorer](/api#api-explorer) and the [API Examples](/api/examples) However, some parameters are particularly dynamic or generic; these may not be explained well by the auto-generated documentation. The format for passing options as parameters using the REST interface is explained at [REST interface](/api/interfaces#rest).
There are many API Options accepted by the CiviCRM API. These options allow the developer to add in more parameters to the resulting Query that is run against the database. E.g. Limit, Sort. You can explore these options using the the [API Explorer](/api/index.md#api-explorer) and the [API Examples](/api/examples.md) However, some parameters are particularly dynamic or generic; these may not be explained well by the auto-generated documentation. The format for passing options as parameters using the REST interface is explained at [REST interface](/api/interfaces.md#rest).