from the response.
> Had it been name-value pair, it would have got populated in my map
> automatically.
>
> Thanks,
> Jignesh
>
> From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Michiel
> Beijen
> Sent: Wednesday, March 20, 2013 4:05 PM
&g
Hi,
On Wed, Mar 20, 2013 at 4:21 PM, Jignesh Kakka (jkakka) wrote:
> Let’s say we add a dynamic field called ticket_source in OTRS.
>
> Now while creating the ticket , there is no problem.
>
> But while getting the ticket, I have to modify my application source code
> to get/read this n
have got populated in my map
automatically.
Thanks,
Jignesh
From: dev-boun...@otrs.org [mailto:dev-boun...@otrs.org] On Behalf Of Michiel
Beijen
Sent: Wednesday, March 20, 2013 4:05 PM
To: Development community of OTRS
Subject: Re: [dev] Issues with Dynamic Fields
Hi,
On Wed, Mar 20, 2013 at 5
Hi,
On Wed, Mar 20, 2013 at 5:33 AM, Jignesh Kakka (jkakka) wrote:
> While creating ticket, we pass Dynamic fields as name-value pair. But
> while getting ticket we receive dynamicFields as DynamicField_FieldName.**
> **
>
> Cant this behavior be changed to having Name Value pair even while gett
While creating ticket, we pass Dynamic fields as name-value pair. But while
getting ticket we receive dynamicFields as DynamicField_FieldName.
Cant this behavior be changed to having Name Value pair even while getting the
ticket.
The reason wh I want in this way is , let's say if we add or remov
