Recommendations for creating custom fields

[Vstory]

When creating a custom field, it is allowed to call an existing field in the database. E.g, My database itself already has an "AndroidApp" field, and when I create a custom field and enter it, KeePassDX should retrieve the field from the database, provide it to fill. Similar to autocomplete for search engines. This avoids creating duplicate items etc. As shown in the picture, the KeePass desktop program does a good job.

[alexanderadam]

I just saw that there's AndroidApp_1, AndroidApp_2 etc in your screenshot. Is that the official convention to do so? Because I used one line per app identifier in a field called AndroidApp.

[Vstory]

I just saw that there's AndroidApp_1, AndroidApp_2 etc in your screenshot. Is that the official convention to do so? Because I used one line per app identifier in a field called AndroidApp.

Yes. For multiple applications using the same login account, it is recommended to use custom field names such as "AndroidApp," "AndroidApp_1," and "AndroidApp_2." This naming scheme is followed by other open-source clients of KeePass.

[alexanderadam]

Thank you for your response @Vstory. Now I created a lot of invalid records I guess.

Do you know whether I can somehow migrate multiline AndroidApp into separate AndroidApp_1, AndroidApp_2, etc entries programatically? Is that possible?

[Vstory]

Do you know whether I can somehow migrate multiline AndroidApp into separate AndroidApp_1, AndroidApp_2, etc entries programatically? Is that possible?

Sorry, I'm not a developer.

[J-Jamet]

Do you know whether I can somehow migrate multiline AndroidApp into separate AndroidApp_1, AndroidApp_2, etc entries programatically? Is that possible?

The simplest solution is to export your database as XML, copy and replace it in an editor, and then transform it back into an encrypted .KDBX file. You can do this with the KeePass2 or KeePassXC desktop application.