Emilie Duveau

Hello Nicole,

Our case is to provide a way for our B2B customers to export the list of requests they can see in their help centers.

As they can see the requests of all people from their organization, it would be easier to have an overview of these requests without the pagination.

Thanks.

Our customers are looking forward to have this.

Graeme,

It worked when I didn't copy/pasted it directly from this page - good to know!

Thanks a lot!

Graeme,

I call the URL https://myzendesk.zendesk.com/api/v2/users/userID.json.

It updates the given end-user. It perfectly works like this for the update of the field "test_trigger".

Thanks.

Hello Graeme,

Thanks for the example, it really fits our need.

However, I have the same error Sheldon got (but I can't find an answer on how to fix it).

I send this JSON:

{
 "user":{
 "user_fields": {
 "last_satisfaction_date" : "{{ 'now' | date: '%Y-%m-%d' }}",
 "test_trigger" : "ok"
 }
 }
}

and I have this result:

{
 "error": "RecordInvalid",
 "description": "Record validation errors",
 "details": {
 "custom_field_values.base": [
 {
 "description": "Base Last Satisfaction Date is invalid (expected a date; try YYYY-MM-DD)"
 }
 ]
 }
}

The update is correctly done for the field "test_trigger" which is a text field.

If I hard-code the date, the "last_modification_date" field is correctly updated.

Any idea about what I miss here?

Thanks a lot!