RDL

I'd like a view of all my items in Enpass that's similar to the Details view layout in Windows File Explorer where I could sort and possibly even filter items using each column. Perhaps the new view would be more like Excel or some generic spreadsheet software. I think I would use Enpass a lot more if it were as user friendly as Airtable. Currently I can see a list of items in the Enpass desktop application similar to the List view layout in Windows File Explorer.

What language would you prefer to do this in? Here's another example using C# - the phone number is on the bottom: http://blog.stevex.net/string-formatting-in-csharp/

This comment is more about this forum than the Enpass product itself. However, improving feature requests would impact the feature request roadmap in Enpass at some point. Anyways, it's relatively challenging to determine if there's a duplicate feature request with 38 pages of feature requests to sift through. It''d be nice if there were filters in the forum's search to narrow down which features have been implemented already in this forum, any categories of feature requests (other than random tags people come up with), etc.

When I enter a phone number I'd like it to be auto-formatted. Currently I setup field type of Phone and type 8003334444, but it doesn't format to (800) 333-4444 let alone if I add an extension. If I type a hyperlink in HTML I can add extensions, but extensions are relatively rare, so I think that could be an additional feature request if you can't find a solution in a reasonable amount of time. <a href="tel:+441234567,88">+44-123-4567 ext. 88</a> There are also fields where it auto-formats as you type. This would be ideal, but not necessary. It could auto-format after I finished typing. http://igorescobar.github.io/jQuery-Mask-Plugin/

Can there be a feature request roadmap built into Enpass? Then users could vote on the features they want most in the program. Maybe users get 10 extra votes per month in addition to 1 standard vote per feature request, so they could weight which feature they need or want. Even if it's just an iframe to a webpage that shows the feature requests that have been: fulfilled queued up to release next backlogged underdefined rejected or cancelled for various reasons