entry sim card

Hello,

Thank you for the request. I would recommend using our "Other (custom)" data entry type for this. I've attached a template you can import with these fields already entered, if it can help.
You can read more about templates on our documentation article here: https://docs.devolutions.net/rdm/commands/file/templates/

Additionally, we would like to improve the "Other (custom)" entry type to make it easier to use, and have more features. I think this would add nice value to our products, since it would save on the back-and-forth needed for us to create a new entry type strictly made for storing information. We've opened an internal ticket for this.

Regards,

Hello,

Thank you for the request. I would recommend using our "Other (custom)" data entry type for this. I've attached a template you can import with these fields already entered, if it can help.
You can read more about templates on our documentation article here: https://docs.devolutions.net/rdm/commands/file/templates/

Additionally, we would like to improve the "Other (custom)" entry type to make it easier to use, and have more features. I think this would add nice value to our products, since it would save on the back-and-forth needed for us to create a new entry type strictly made for storing information. We've opened an internal ticket for this.

Regards,

@Hubert Mireault

Hi Hubert, that would be really great. i find the current Other (custom) data entry very difficult to use. too many clicks to get the information needed whats stored in the custom entry. but currently no other option to store this kind of data.

many thanks also for the template :-)

Thanks for the feedback, it's at least good to get confirmation that the "Other (custom)" entry has some friction in how it's currently designed and that reworking it might help more users adopt it.

I was thinking of changing the UI so it's more similar to the way the "more custom fields" are handled:

So, rather than having a grid which requires you to select an item > view > copy the value, you would have it all available with more traditional text fields, avoiding a few clicks. The adding and removing of fields would also be easier, we could more easily support different field types (like date/time, numeric, etc), and a few other things like that. We would have to figure out a way to make the fields more compact, but I think with some smart thinking it should be possible to arrive at something versatile and frictionless.

Let me know if I'm on the mark regarding usability, or if you have any additional ideas or specific pain points with the "Other (custom)" entry and we'll see if we can address them at the same time.

Regards,

Hello,

The “Other (custom)” entry has been reworked and renamed to Custom record. This improvement addresses the usability issues you mentioned, and should be available in version 2026.2.0.

The new version removes the grid and allows fields to be directly viewed, edited, and copied. It also introduces field types (including sensitive fields), per-field copy buttons in the dashboard, and quick access to frequently used values.

Your SIM card use case should fit much more naturally with this updated entry.

Regards,