RELATED IDEAS
Custom table data migration between product lines
The structure of our organisation (and subsequently its product lines and workspaces) are prone to change on an annual basis. It is currently easy to change parent lines, however the data will always be kept in the original product line, meaning we cannot delete it yet need to allow users to see it in the menu.
Example
Product Line A contains 5 Initiatives under 'Strategy'.
We now want to split out Product Line A to 5 separate Product Lines (with 1 Initiative each) due to stricter permissions for viewing data.
We can use 'Move initiative' to separate Initiatives to their respective new Product Lines. However their existing data will always stay in Product Line A.
Product Line A is now a redundant Product Line, but we can't delete it. We rename this to '(Ignore) Archive' because users still need access to it for historical data.
-
ADMIN RESPONSEMar 1, 2021
Thank you for your idea. It is currently possible to move custom table records between workspaces and parent lines.
From your custom table, click the more options
...icon and select View as a list report. From the list report, you can select multiple records then bulk edit them to change their workspace.
© 2024 Aha! Labs Inc.•All rights reserved
Thanks for your response. Unfortunately we started with 1 "archived" product line to 30+ product lines with 7 custom tables each. Which means we'll have to conduct this exercise 210 times (potentially). It'll be much easier to inspect the data contained in the 1 "archived" product line and choose what data to reallocate, rather than the other way around. Thoughts?