Resource Dependencies in Information Design Tool
For any local resource, you can view its relationship to other local resources, and any dependent universes published in a repository.
Making changes to a resource, such as deleting it from a local project, moving it to another local project, renaming or updating it, may impact other resources that depend on it. You are warned of the impact before you delete or move a resource.
Dependencies between local resources
The Show Local Dependencies command shows the dependencies between resources in a local project.
When you select a resource, two tabs display the dependent and referenced resources: The Dependent Resourcestab lists resources in the same local project that depend on the selected resource. The Referenced Resources tab lists the resources in the same local project that are referenced by the selected resource.
To see the local dependency on a business layer, right click on the business layer name and hit Show Local Dependencies.
I have hidden the database connection name( .cns name) in all the images used below.
When you click Show Local Dependencies you see two tabs
The paths to referenced resources are relative, not absolute. That means that if you rename a resource, the referenced resources are assumed to be in the same folder. If the referenced resources are in a different sub-folder, the reference is broken.
You can also show local dependencies for any object in the business layer. In this case, for relational business layers, the referenced resources include the data foundation tables and columns that the object is based on.
Now let’s see what breaks the links while renaming.
First rename the Business Layer name from Sales & Selling Universe to Sales & Selling NEW Universe and check the Show Local Dependency.
The following dependencies are displayed:
Even though the business layer was renamed, the datafoundation is listed as a referenced resource because it is in the same folder.
Now, create TEST Sales Universe project and copy Sales & Selling Universe.blx to this folder. In TEST Sales Universe, rename Sales & Selling Universe.blx to Sales & SellingNEW2 Universe.blx and show local dependencies.
The reference to datafoundation is broken because when renaming to to Sales & Selling NEW2 Universe.blx, the information design tool assumes referenced resources are in the same folder.
Dependencies between data foundation and business layer objects
When editing a data foundation, you can show local dependencies for any table or column. A list of dependent business layers displays. You can then display a list of the objects per business layer that depend on the selected data foundation object.
When editinga relational business layer, in the data foundation view, you can select tables and columns and show associated objects. This will highlight in the business layer all objects which reference the selected data foundation objects.
Nice blog and nice example.
So how to fix this issue?
Facing the same issue.. Do we know how to fix this?
1 way to fix it and 1 workaround.
To fix it, delete the objects using the referenced resource.
But in most cases you don't want to do that because you need the object.
So the work around.
Create referenced resource.
Download your resource from the again to a local folder and rename it to match the referenced resource. The reference is only design-time and not runtime so once it is published it doesn't matter.