Re: [otrs] Dynamic Fields... direct access in the DB

Hops… answer to myself SELECT id, name, trim(regexp_replace(line, '.*:([^:]*)', '\1')) as value_text, trim(regexp_replace(line, '([^:]*):.*', '\1')) as display_name FROM (SELECT dynamic_field.id, dynamic_field.name, regexp_split_to_table(dynamic_field.con

Re: [otrs] Dynamic Fields... direct access in the DB

Hello Renée, Thank you for your idea. This is definitely an option - I could even create this table automatically at the beginning of my SQL query using WITH or something similar. Although doing this purely in SQL is not a super-ex

Re: [otrs] Dynamic Fields... direct access in the DB

Hi, I would do it that way: * Create a new table wingo_df_values (field_id, field_key, field_value) with unique (field_id, field_key) * change the backend module for Dropdown fields where the possible values are stored to the new table (every time the dynamic field is changed) * use that new

[otrs] Dynamic Fields... direct access in the DB

Hello dear list, I’m trying to export a list of tickets directly from the OTRS DB - I’m computing 20 columns, there are 7 joins… the request is not that small… And it takes approx. 50 seconds to generate 5’000 rows I need. Knowing that I will eventually need to export much more than 5’000 rows,