Why DSS import behaves differently than export for bundle which is already exists
Hi
Why DSS behave differently when user tries to export/import bundle zip file, which is already exists by its name?
In export, the UI throws "Bundle ### is already exists for project ####", and marks it with error.
But in import, it doesn't give any warning, just overwriting the bundle and changes the import info date. Why it doesn't have same exception as export, or at least some warning or other info.
Answers
-
CoreyS Dataiker Alumni, Dataiku DSS Core Designer, Dataiku DSS Core Concepts, Registered Posts: 1,150 ✭✭✭✭✭✭✭✭✭Hi, @arielma2304
! Can you provide any further details on the thread to assist users in helping you find a solution (insert examples like DSS version etc.) Also, can you let us know if you’ve tried any fixes already?This should lead to a quicker response from the community. -
There is no real example, only trying to understand DSS behavior, and how come import just override the existing version if exists with no warning or exception (unlike export bundle action)