<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 15-10-2014 20:08, William Clarke
wrote:<br>
</div>
<blockquote cite="mid:543EB819.5020202@simons-rock.edu" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix"><font size="-1"><font face="Calibri">RT,<br>
<br>
Little more info...<br>
<br>
I have migrated\updated rt3 database to a fresh install of
rt4.2.8. So I can bounce back and forth between rt3 database
and rt4 database with $DatabaseName in RT_SiteConfig.pm.<br>
<br>
rt4 database has "RT::Extension::Assets" plugin working
however the tables (rtxassets, rtxassets_id_seq,
rtxcatalogs, rtxcatalogs_id_seq) aren't populated due to
this being a fresh database.<br>
<br>
old rt3 build\database on the other hand had
"RTx::AssetTracker" installed so it has the following
tables\sequences that rt4 does not (at_assets,
at_assets_id_seq, at_ips, at_ips_id_seq, at_ports,
at_ports_id_seq, at_types, at_types_id_seq)<br>
<br>
</font></font></div>
</blockquote>
<font size="-1"><font face="Calibri">My plan of attack:<br>
- generate for all assettypes a seperate rt_config.pm which maps
the CustomFields to the right Catalogs<br>
- generate a search to export each assettype to a csv file<br>
- import using the RT::Assets import tool to import them
maintaining the ids<br>
- write a small perl script to walk all
tickets,articles,old_assets looking for links to old_assets and
relink them to the new_assets.<br>
- drop the old tables.<br>
<br>
In concept this should work I think but I'm open to better ways
todo this since its error prone and a lot of work.<br>
</font></font>
<blockquote cite="mid:543EB819.5020202@simons-rock.edu" type="cite">
<div class="moz-cite-prefix"><font size="-1"><font face="Calibri">
Installing AT3.0 has given me some issues with both rt3 and
rt4 database. It appears it's no longer supportd after
rt4.0.0. We were hoping you guys could shed some light on
this for us. How can we migrate our old Asset Tracker data
into rt4 database or maybe get rt3 database fully functional
on 4.2.8. <br>
</font></font><br>
</div>
</blockquote>
Had the same problem and 'fixed' that in testing by looking at the
error and where it was generated. From memory it was about a
CustomField type of thing.<br>
<br>
Joop<br>
<br>
</body>
</html>