Anyone,
Retrieved the universe in IDT. Was working on it but did not publish, just saved. Had a brilliant idea to retrieve the same universe again in to the same project. Deleted without modifying or saving the second version of retrieved universe. Now trying to publish first retrieved universe that I worked on in the project but I am getting the error "An error occurred while loading the universe. Your universe contains broken links. Please fix them before publishing the selected universe"
I think it is something to do with data foundation file (.dfx). How do I fix this problem?
I cannot find much on this issue in SAP docs.
Thanks in advance for help
This is a hack that I discover and it solved my problem. I do not know if this is the way to go and will welcome the correct way of solving this problem if any.
First you have to have admin rights on the machine where IDT is. With that said, I went to the folders options properties and unhide the hidden folders. Then I located the folder where IDT saved my projects and retrieved universes. From the error message that IDT gave me I got the name of the missing retrieved folder that I deleted. I created the folder with the name from the error message and copied content of the folder that I had in to the created folder. After this everything worked.
Believe it or not but this was trick that allowed me to publish my universe.
Thanks for the tip… that worked for me!
I had to wipe my cache in IDT post a migration.
(which can be found here C:\Users\user_name.businessobjects\bimodeler_14)
So I was starting from scratch
I had to create a project with the same name… then create the two folders… then copy my current retrieval into those folders.
Follow up that leads to a question…
I can now export the UNX to the repository, which is nice… BUT if a teammate retrieves that UNX, they CAN’T export it without doing the same fix…
So either Ill need to instruct my team to create a local project with the same name and send them the old folders they will need to copy into their IDT cache
C:\Users\user_name.businessobjects\bimodeler_14\workspace\PROJECT_NAME folder.
OR (Best Choice for US)
Create a shared project
Push local copy to server via Project Synchronization
Have teammates pull down the shared project.
Most of the team here still uses universe design tool not IDT… This is the first instance that led me to think well need Project Sync
Id like to know why I have broken links to my old retrievals and why that gets stored in the UNX for my teammates to enjoy… I did read somewhere that it could be tied to objects copied from other UNX… Meaning I copied an object from one retrieval and pasted it into the current unx… Totally possible.
Does anyone know how to determine which objects that might be do I can recreate them and delete the objects causing the broken links to begin with?
I had the same problem…
The reason for my problem was that the columns in Derived tables have changed.
Just in case someone is having the same problem… try integrity check on the business layer and fix the errors if any.
SAP IDT and “The universe contains broken links. Fix the links and try publishing the universe again”
In my case this was an issue directly related to copying objects from another unx and incorporating into existing unix. The “broken link” can be resolved in deleting the LOV for the objects that were copied over from the other unx.
steps took to remove link
-Run integrity check on the unx. I found the objects that were the issue showed in the integrity check as, “The resource ObjectABC was not found”. This object needs to be resolved.
-in my case I selected the object then went to the Advanced tab. I noticed the LOV object stated, “error”. What I assumed happened here is the error shows because it was copied over from another unix. I hit the ‘X’ and this cleared up my issue. You can see that it deletes the broken link by going to the blx from the projects view and right clicking to “Show Local Dependencies”. Then go to the Referenced Resources and no longer see the broken link.
-From this point I was able to export without issue.
Guys,
I had this problem again, on another system, and I believe I have found the proper solution.
To fix, run Check Integrity → Connections and Dependencies → Check Dependencies.
This will discover objects with broken links. Investigate them carefully and fix the problem.
For me it was broken List of Values for two dimension objects, these objects were initially copied from another universe and I do not remember if I checked the LOVs after copying
An improvement to this. I ran into the same issue, and solved this way:
1 - close IDT and navigate to where your UNX is stored
2 - open the .blx file with winrar (Yes! Behind the scene, both .dfx and .blx indeed are .zip files!!! 8) )
3 - extract the .deps file and open it with an editor (it’s an XML file)
4 - search for the guilty link (you will find one occurrence only)
5 - modify the string with the expected path (the one of your local project)
6 - save the .deps file and store it back on the .blx file
Now, if you reopen IDT, there shouldn’t be any more broken links in local dependencies.