Re: Migrating free text 3.0 to dynamic fields 3.1
Juan Manuel Clavero Almirón <juanm.clavero <at> ibsalut.es>
2012-05-29 14:48:40 GMT
I'm afraid I asked after reading the code, but before really trying it.
My first attempt was on a freshly installed test-environment OTRS-3.1.5. I dumped my dev-OTRS-3.0 ticket
data in this 3.1-dev and THEN made the upgrade as explained in UPGRADING, step 8. And it didn't go well, of course.
Now I've duplicated my dev-OTRS-3.0 and upgraded it to OTRS-3.1.5, as explained, and it worked
seamlessly: all my freetext are there, even the 200 options of one of them, and they are visible in the same
windows as they were before.
So, here's an apology for asking beforehand and a gratitude to all OTRS developers for such a well-done task
| Date: Thu, 17 May 2012 07:41:49 -0500
| From: Carlos Rodr?guez <carlos.rodriguez <at> otrs.com>
| Subject: Re: [dev] Migrating free text 3.0 to dynamic fields 3.1
| To: Development community of OTRS <dev <at> otrs.org>
| Message-ID: <5D57F2C4-25CA-4FB6-A68E-5C448E6E7417 <at> otrs.com>
| Content-Type: text/plain; charset="windows-1252"
| Hi Juan Manuel,
| The DBUpdate-to-3.1.pl script is designed to take ALL the free fields from ticket and article and
transform them into Dynamic Fields, so if the fields you have for Building and Location are standard otrs
free fields (e.g. TicketFreeText2, TicketFreeText15, etc) they will be converted (including their
values)... That's the main idea of this script
| If the fields are not standard otrs free fields (I mean if you have customized the screens and add columns to
the database to have something like TicketFreeText17 or TicketFreeText32) for sure the script will not
migrate this kind of customizations.
| Please notice that the configuration of the Dynamic Fields is different from the Free Fields, while the
screen configuration (to display or hide Dynamic Fields per screen) is still in the sysconfig (and should
be also migrated with the script), the Dynamic Field configuration is in a separated screen in the Admin
Panel, with this new screen you can manage your fields, you can add or edit fields.
| If your fields are defined as dropdown (a list of predefined values) you can choose in the field
configuration if you want to translate the values or not, otherwise if the fields are defined just as input
boxes (Dynamic Field type: Text) the values are not translated.
| Also notice that if the script detects that an old free field is not in use it will mark it as disabled Dynamic
Field, but the rest of migration process will be the same.
| I hope this clarify your questions.
| While we have been testing the upgrade process and the particularly the script , I still recommend to
backup the database before the upgrade and/or first migrate a test system before touching the production instance.
| Carlos Rodr?guez
| On May 17, 2012, at 3:19 AM, Juan Manuel Clavero Almir?n wrote:
| > Hi all,
| > although OTRS 3.1 has been out for some time, I?ve started looking into it this week, in order to safe
upgrade our systems.
| > Currently, we are using 2 freetext fields to store the current location of the customer: one for the
building and the other for the location inside this building. Our buildings have names in our local
language and there?s no point in translating them.
| > I?ve seen there is the script scripts/DBUpdate-to-3.1.pl, which moves the freetext stored in ticket
table to dynamic field values. But it seems to me that it will only move the free text fields that OTRS uses
(i.e. Decision Result and Due Date).
| > Am I right?
| > If so, Would it be difficult to grab the free text config in 3.0 and insert into dynamic fields in 3.1?
| > Kind regards,
| > Juan Clavero Almir?n
| > _______________________________________________
| > 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
OTRS mailing list: dev - Webpage: http://otrs.org/
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev