Support customfields on more entry types
1 vote
After exporting our vaults from the server version and import into Hub, we have noticed many entries have lost their customfields where we have stored data which can no longer be accessed via the Hub.
So we have kept our old devolution password server online.
The bare minimum for me would be to be able to migrate 1 to 1 between your own services which we cant 100% do, when theres a few entries that dont even exist in Hub but do in password server, and fields are not shows.
An example of this is old certificate entry, in hub the entries are just called document after import.
Custom fields are shown when viewing the entries in RDM and connected to the Hub, so the data have been imported they just need to be shown.
Connection-String as an entry cannot be added in Hub as a new entry, but old ones have been imported so the entry type exist since it recognize it as "Connection-String"-type.
All Comments (7)
Good Morning and thanks for your feedback.
Regarding your issues, I will create two internal tickets:
One to investigate the Custom Fields not showing in the Entry type Document (look more like a bug).
Another one to add the Connection String as an Entry Type for the Hub.
We understand your expectation to be able to migrate your data from both systems, in the meantime, do you have any other specific Entry Types that are causing issues during your import?
Finally, as a temporary workaround (Read-Only), please note that you can view these fields values via the View Raw Data tab (see screenshot). We are aware that this is not a perfect solution, but it should allow you to view the values of your fields in the Hub while we work on these tickets.
