Skip to content

Detect orphaned profiles resulting in duplicate entries in UI #29

@Chris15294

Description

@Chris15294

Per our discussion

take the dronbot
there used to be a profile option 1, and we store things against the lowest number
so in the catalogue, there is an image for option 1
(of profile 1 of unit 17).
the part of the code which decides "is this going to have a model we can at least fall back on" is just checking that there is at least something for that unit, but the actual writer is looking for the profile
Thinking on it, if I can pull out the equivalences for the now deleted models, I may be able to auto update it. Otherwise I'm just going to have to add a 'detect orphans' button which dumps them all out to a list before deleting them from the catalogue and you'll have to manually readd them.
On the plus side, it does look like there is only 20 or so units affected

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions