Hello,My last ticket about this has been closed so I'm having to start a new one as I can see no way to re-open it.I have three bespoke fields from my 1.6 ST installation (customer, product & version) that I have imported into three dynamic fields that I have created in a test 1.9.3 installation (into the ost_form_entry_values table). Initially I left my own bespoke customer field and read it from the data that was imported when I upgraded from 1.6 ST to 1.9.3 (via 1.7.5) as it is not possible to define a list that reads entries from a table in another database. However, I decided to create a dynamic field, Client, with an associated list and I wrote a script to populate this list from the other database/table. I intend to run this script regularly to add any new customers to the list.This all works fine for displaying in tickets and I have modified staff/tickets.inc.php and staff/ticket-view.php to display these as I require. I have written a new class that contains my bespoke functions for retrieving and formatting these fields for display so that I don't have to edit any existing classes.My problem is that the Advanced search doesn't work by default on the dynamic fields. I have discovered that the data needs to be written to the ost_ticket__cdata table. This currently has columnsticket_id,client, client_id,product, product_id,version, version_id,subject,priority, priority_id(created by osTicket) and contains one row per ticket.I managed to get the Advanced search to work correctly on the client field by updating the client_id to be the corresponding value_id value from the ost_form_entry_values table for each ticket. I tried to do the same for the product_id and version_id values and this worked fine: I could do Advanced searches across any or all of my dynamic fields.However, after creating some more test tickets and editing others the Advanced search stopped working on all but tickets created with osTicket. If I run my script to update the client_id, product_id and version_id fields the Advanced search works again. So clearly, somewhere during the updating of tickets these ost_ticket__cdata column values are being changed. Either what I did was incorrect or, possibly insufficient. What I did to the column entries in the ost_ticket__cdata table was based upon entries that I observed had been made by the "system" for newly created tickets. However, I'm working blind as I don't know how the different tables all fit together.Could I have some advice about how to proceed?ThanksMike
