Error while migrating discoverer Workbook

Question

Hi All,
I am migrating Business Area and Work book from one instance(QA) to another(Production) DB instance.
I have successfully did export of business area and import in production instance.
For workbook migration I have followed the below mentioned steps.
1) Open QA instance and open the required workbook.
2) Do "Save As" of the workbook to local machine as ".DIS".
3)Then Login to Prodcution Open the workbook from the local machine. But in that case it gives following error
" Cannot join tables.Item dependency "" not found in EUL. "
"Attempt to open workbook failed" Anyone can help me to solve this issue. Please.
Thanks
Alaka

Answer 1

Hi Janet
Here are some more notes from my private collection of tips and tricks:
Discoverer workbooks are very picky when it comes to opening up against an end user layer. Basically, here is what happens:
All EUL objects have an ID number and a name. When Discoverer saves a workbook it saves both the ID number and the name of every essential object (business area, folders, items and joins) that is used within the workbook. The next time Discoverer opens the workbook it looks at the ID numbers of the objects and tries to find them in the EUL. If it cannot find an object by its ID number it tries to locate it using the object's name. If an object cannot be located either by its ID number or by its name you will get the dreaded Item Dependency error.
OK, having got that out of the way, if you delete a folder from within the EUL and re-create it you will lose the ID number of the folder and all of its associated objects (items and joins). The only way Discoverer will be able to open this workbook now is if everything within the folder is named EXACTLY the same way (including underscores and casing of the name), otherwise the workbook will not open. Discoverer will report the error message that you are seeing.
So what can you do? Well, you need to have some way of finding out what the old folder name(s), item names and join names were. Also, you need to make sure that all items that were not hidden are not hidden now. There is no need to worry about the names of hierarchies or lists of values. These are not stored within a workbook and are only hooked in at runtime.
Seems like you have to somehow painstakingly determine what all of the item and join names were in your old folder(s) and re-create them 100% the same way in the new folder(s). By the way, when the workbook gives you the error message does it also give you an opportunity to assign al alternative item to the item that it can no longer find a value for? This may work but, in my experience, usually doesn't!! It only works if the missing dependency is an item, it won't work if the error is being caused because you have got a join name wrong. Unfortunately, joins MUST have the same name exactly otherwise there is just no way to open the workbook.
Best wishes
Michael