a month ago
The longer I am using Datasphere, the more frustrated I become about some design choices and at this point I am wondering if I miss something.
I have a very simple landscape with a dev Datasphera and a prod Datasphere. Most of the time, I want to transport medium sized changes to already existing models and views.
Currently, you can either use packages, where you always have to grab all dependencies but you do have the option to organize all changes into some sort of "unit" or "package" or you do it manually and you might forget to transport a change you made.
So exactly the option that I need the most: Package a few changes into a transport without the entire dependency chain, is missing.
All I need is the ability to create a package without all the dependencies. Very simple! And that is how the transport management works in SAP R3 and R4? What was the reasoning not to do it with Datasphere?
On top of that, the UI is especially slow there. Simply opening the initial dialogue takes 30 seconds.
What it all boils down to is that even minor changes that should be 5 minutes take me 30 minutes because of the clunky and slow implementation.
But I cannot rule out, that I do something wrong so I am here posing the question if other people see it the same way or if make mistakes.
Request clarification before answering.
Hi,
We're not using the Package menu but using the Export menu, when creating a new Export (package) there is an option to press CTRL when selecting items to select the objects without their dependencies.
Maybe the Export option is what you had in mind when you said "do it manually" in which case this feature might not answer your question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
50 | |
10 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.