Hi Everybody
I have a multi source data foundation which was used to create various business layers which were published as universes (BI 4.1.sp7).
Now I need to develop a new data foundation which, initially, is exactly identical to the old one but it will evolve over time. The old one will stay at the root of the current universes, which will become legacy, the new one will sit at the root of other, differently designed, business layers/universes. I need old and new to keep working in parallel because many reports reference the legacy and they will be changed piecemeal.
in practice
now I have X.dfx -> a.blx,b.blx
I need to create Y.dfx_->c.blx,d.blx
X.dfx=Y.dfx at the beginning. X.dfx will stay as it is, Y.dfx will evolve.
This is what I did to create Y.dfx.
created a new project in IDT.
copied the X.dfx into the new project (copy paste in IDT)
renamed the X.dfx to Y.dfx ( "logical" name updated to Y too).
Now, if I check the new data foundation repository dependencies, I see the legacy universes as dependencies of the new .dfx. It is as if the new .dfx, created by a copy is not distinguishable by the old one.
in practice:
repository dependencies of X.dfx = a,b
repository dependencies of Y.dfx = a,b,c,d
My concern is that, when I will edit the new data foundation and I will re-publish the new universes based on it, the legacy universes will be affected somehow and they will break.
Any idea?
Thank you very much.
Gus
Hi Gus,
After copying the .dfx from one project to another did you renamed the .dfx from the local project only or you also renamed it after opening the .dfx from the summary window as well?
If it still points to the a and b blx, then I think the reference lies with the connections (@catalog - short name gets added in the sql).
For this create new connections, then change the connections of the copied dfx and see if it helps.
Regards,
Adil Raj
Add a comment