Question on importing Universe

I’m just starting to import Universes to production. We are on XIR2 SP1 We have not previously used the import wizard to move anything to production. We are currently using only using Crystal Reports in Infoview and those are posted directly to production from Crystal Developer.

I am planning to use the import wizard to move my universes to production from our dev server. The import options are to

  1. Merge using the title to determine if it exists
    or 2. Update destination system using the objects unique identifier.

It makes sense that I want to update (option 2), esp after the first time I put the universe on prod. However I have a concern about option2.

Are the unique identifiers for reports and universes different? In other words, could the unique identifier for my universe on dev actually match a unique identifier for a report that exists in production? And could I potentially update a different object that I intend to?

I hope this makes sense. Thanks for any help


slf100 :us: (BOB member since 2006-11-15)

My understanding is that every “object” (and I use the term here to mean repository object, not universe object) has a unique ID. If you look at the CUID by itself you have no idea what it references because there is no type associated with it. So if the CUID is the only way to match items up from TEST to PROD you could in theory overwrite a report with a universe or vice versa.

I had a quick conversation with one of the folks here that does our migrations, and he believes that both the CUID and the name of the object need to match in order to migrate successfully. That would mean you would not be able to overwrite a report with a universe, even if they had the same CUID, because the name would never match.

I say “never” because the file type (.unv versus .wid) would be different.

I have no idea if this is correct, so it would be interesting to find out if someone has tried to do this and can report back the real results instead of my speculations. :slight_smile:


Dave Rathbun :us: (BOB member since 2002-06-06)

I think what Dave says is correct, but would be interested if someone had actually done this, also.

The best explanation of IDs I have found is in David Brockingtons explanation, pages 66-67 in his Lifecycle Manager presentation, here:-

https://bobj-board.org/t/120212

It doesn’t answer your question, but is a good insight nonetheless…

I think you would be wise to base line your systems and formalise your development process, by putting your Crystal content into Dev…


Mak 1 :uk: (BOB member since 2005-01-06)

Thank you both for your comments. They were very informative.

Thinking back when we created dev, I believe we did do an import of the reports from prod at different points so most of the CUIDs may actually be duplicates except for a few newer reports. Our dev was used more to test security and then create universes since it’s creation. I see two options. Take the risk one universe at a time. Monitor to see if any reports “disapear” and recreate on prod. Once all the universes are out, resync prod to dev.

Or recreate dev from prod to sync the CUIDs initially. I’m concerned about importing from prod to dev from scratch to sync the CUIDs. Would I be able to save my universes and connections off then reintroduce them to dev so that I don’t have to recreate them?

I think I figured out how to query to look for the CUID, so I think I can determine if anything else exists out there with that CUID. I’m querying both ci_appobjects and ci_infoobjects.

Thanks again for all your help.


slf100 :us: (BOB member since 2006-11-15)