Transporter improvements: ability to edit transporter packages, display physical names of DB objects

Anastasia Pesyakova
Employee




Hi!
I have recently migrated the changes from sandbox to production on Board Version14.1 Revision 0.0.208107. I would like to suggest some improvements to the transporter functionality that should make the migration easier:
- Add the ability to edit the transporter package, whether it's a data model package or a capsule package. Currently the edit button allows to adjust only Options: run/not run a DB backup and enable/disable a DB Maintenance Mode. We can't adjust the contents of the package - the selection of objects to transfer from source to target. In case the edits are needed, we have to recreate a transporter package.
- Display the physical names of DB objects in addition to the admin-defined names when creating a package. E.g. different cubes can have the same admin-defined names on source and target environments. It takes time to identify which objects should be kept or overwritten when their physical names are not displayed.
Thank you!
Anastasia
Tagged:
17
Comments
-
@Anastasia Pesyakova Thank you for submitting this! These improvements would have been incredibly helpful during the migration process.
1