Catalogue Migration to Framework Manager

[sparked]

Hi,

About to start migrating a 7.3 catalogue to 1.1 MR2 Framework Manager and was wondering if anyone had any tips or anything in particular to look out for.

I've got as far as importing the .xml version of the catalogue into a new framework model / project using the migration utility, however its thrown up a stack of verification warnings. (Dunno if these are significant or not at this stage)

Was wondering what the consensus was on this process, if its worth it, how much time you spend after importing the catalogue, what sorts of 'tidy up' tasks you end up having to do etc. etc.

Any insights on this very welcome.....

Also looking to migrate report sets and same question applies, i.e. are there any features in impromptu reports that don't tend to migrate like maybe datasets in filters, multi query reports etc. How 'clean' migrations actually are, and when perhaps its better to consider redeveloping a report rather than migrating it.

Many Thanks,

 

[KingCrab]

I would redo it from scratch. That will be the best route in the long run and save your from prematurly losing all your hair.

 

[sparked]

I might have to justify that decision ! What sort of problems did you encounter and what problems does this cause in the long run ?

 

[sparked]

Anyone out there who's done a migration who can contribute ??? Ideally looking for specific examples of things that don't migrate e.g. catalogue prompts, certain joins types etc. or anything that caused a headache.

Any thoughts welcome !