Updating custom fields with @ by mail
Hi
I have 2 custom fields in my queue called external_reference and order_number I'm trying to poke values in by email, but I keep getting this sort of error. Can anyone tell me what I'm doing wrong?
[hr]
While handling your mail to IT Support, the following errors occurred:
Cannot assign to custom field of type "": "custom_2".
> From: Hugh Foster <Hugh.Foster@Servisair.com>
> Date: Fri, 15 Jul 2011 10:37:25 +0100
> To: Test KACE <Test.KACE@Servisair.com>
> Subject: [TICK:0001] update
>
> @order_number=T54956
[hr]
The field looks like this
CUSTOM_2 order_number Not Required Owners Only - Visible to Users
I have 2 custom fields in my queue called external_reference and order_number I'm trying to poke values in by email, but I keep getting this sort of error. Can anyone tell me what I'm doing wrong?
[hr]
While handling your mail to IT Support, the following errors occurred:
Cannot assign to custom field of type "": "custom_2".
> From: Hugh Foster <Hugh.Foster@Servisair.com>
> Date: Fri, 15 Jul 2011 10:37:25 +0100
> To: Test KACE <Test.KACE@Servisair.com>
> Subject: [TICK:0001] update
>
> @order_number=T54956
[hr]
The field looks like this
CUSTOM_2 order_number Not Required Owners Only - Visible to Users
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
cblake
13 years ago
So are you using @CUSTOM_2 or @ORDER_NUMBER ?
Haven't tried to set a custom field with the operators, and they aren't documented to work, but if they do it'd be the @CUSTOM_2 value.
I'm also assuming CUSTOM2 is a text field, not a single or multi-select type...
Haven't tried to set a custom field with the operators, and they aren't documented to work, but if they do it'd be the @CUSTOM_2 value.
I'm also assuming CUSTOM2 is a text field, not a single or multi-select type...
Posted by:
Acedashdog
13 years ago
I was kind of working from this bit of the manual:
[hr]
[right]Setting or changing custom fields using email
You can also set any custom fields in your email using the same syntax:
@custom_fieldname=newvalue.
The custom field cannot include empty spaces. Use an underscore between words,
for example, new_value.
You can also use:
• @priority = high
• @priority = very urgent
If you put a bad value into a select or multiselect custom field, an error results.
Use a comma-separated list of values for multiselect custom fields.[/right]
[hr]
I've tried both @CUSTOM_2 and @order_number in a variety of cases and nothing seems to work.
[hr]
[right]Setting or changing custom fields using email
You can also set any custom fields in your email using the same syntax:
@custom_fieldname=newvalue.
The custom field cannot include empty spaces. Use an underscore between words,
for example, new_value.
You can also use:
• @priority = high
• @priority = very urgent
If you put a bad value into a select or multiselect custom field, an error results.
Use a comma-separated list of values for multiselect custom fields.[/right]
[hr]
I've tried both @CUSTOM_2 and @order_number in a variety of cases and nothing seems to work.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.