Re: How to find the link btw ticket and dynamic_field value ?

Juan Manuel Clavero Almirón <[email protected]>
Newsgroups gmane.comp.otrs.devel
Message-ID <4E6C4135180B424CBFC6C6DE9456154A0CB6CC52@SCPDPSEXMB01P.ssib.local>
Hi Stefano,
I think the info you are looking for is in the dynamic_field_value table.
The object_id field may be an article or a ticket, depending on the dynamic_field pointed in the dynamic_id field
Hope it helps

Kind regards,
Juan Clavero Almirón

----------------------------------------------------------------------
| Date: Fri, 25 May 2012 15:07:29 +0200
| From: Stefano Boccanera <[email protected]>
| Subject: [dev] : How to find the link btw ticket and dynamic_field
| 	value ?
| To: developer list OTRS <[email protected]>
| Message-ID:
| 	<CAHMQiK5nQcN10_8+vkH=jNqp_E0k1q849fLcAJS3o4cUnj3z+g@mail.gmail.com>
| Content-Type: text/plain; charset="utf-8"
| 
| Hi
| I migrated from otrs 3.0.9 to 3.1.5.
| All sounds fine, after I migrated the DB (postgres 8.4), but I didn't find how the ticket are linked to the dynamic fields created.
| 
| This information are vital for me, because I have many automated reports using specific sql select.
| 
| So before to migrate the production installation I have to modify any select to output the right informations.
| 
| I just saw to the OTRSDatabaseDiagram.png, but no link relation is depicted btw ticket and dynamic_field or dynamic_field_value tables.
| 
| I suspect, after a very brief cross analysis, that object_id column into dynamic_field_value table contains the ticket id reference, but an extensive check is a very  time consuming job.
| 
| So anyone can help me on this information?
| 
| best regards
| 
| --
|  *
| Stefano Boccanera*
|
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.