Garima, thank you for the reply. Fortunately for me, I had only changed the category of 2 items, from Login to Password. I will now delete those two items, then re-add them directly to the Password category.
I am fairly new to Enpass, so I'm still on the learning curve. Just tonight, I learned that data fields are not associated directly with a category. Instead, data fields are associated with a template, and when creating a new item, we pick the category, and then if the category contains multiple templates, we select the template. My misunderstanding comes from working with the Password category, which apparently has only one associated template, so we don't get prompted to select the template.
But I still think the current implementation is faulty. The Password category has only one template (which I'm guessing may be named the Password template), but I was allowed to change an item from the Login category using the Default template to the Password category. Since the Password category only allows the Password template, the app should not have permitted the move of an item with the Default template to the Password category.
I appreciate the flexibility that has been built into Enpass, but I think it will end up causing many users confusion. Enpass allows me to Add Field or Add Section to each individual item, and even to remove sections from existing items. Instead, I think those capabilities should exist only for Templates. That way, all items using a particular template would all have the same sections and fields. Between a category being able to contain any template via the Change Category action, and individual items being able to add or remove sections and fields, there's a strong possibility for data inconsistency. We can't expect the end user to remember all the changes he or she made over years of use to cause this data inconsistency, so better to prevent it in the first place.
Thank you.