I'd like to be able to search and sort the users table, add custom fields, link to it- basically, the User table should have all the same functionality as any other table in trackvia. Custom views and permissions too.

Right now a person in any role who creates a new record always sees the same form when they do that- I'd like to be able to designate different forms as the 'new record' form based on context, so, for example, different default values can be set in the form, or only fields relevant to the context are shown.

Being able to print the forms for all records in a view would be extremely beneficial. Being able to do this and at the same time do a merge with a template from word or something similar to format an invoice or the like would be HUGE

When sharing a view, the columns expand so much that not all fields show and the data wraps (regardless of how the view looks in TrackVia. The only way to accurately display the info is if the person is a user in the system.

Please add back in the document merge function that was present in Track Via Classic. Using Zapier with WEbMerge is not a valid option given the extreme expense of WebMerge. Be able to produce documents from within a product should be a no brainer. Please bring this back, as the lack of this feature will cause us to look elsewhere

Allow users without admin access to view the history of a record.

It would be great to be able to delivery notifications dynamically to an email address contained in a field in the record that triggers the notification, instead of only to a predetermined person/role.

Like when you're buying a round-trip airplane ticket- the 'return flight' defaults to after the date of your outgoing flight. I'd like to able to set a date field in a form to default to the value entered in another date field already.

I would like to see some type of error handling on the Image field.

Currently, this field will accept any type of file with no error being returned to the user. The result being that no one can see or access the attached file when it is not an image.

The Image field should only accept images and nothing else.

Validation rule needed to prevent two dates from conflicting with each other. Example: "Next Review" should be later than "Last Update"

We're able to add webpages in a widget, but I would love to add HTML or pictures, or even just some text as a widget to dashboards.

This way I could write explanation / rules for all my users about the views and forms I put on the dashboards.

We work in 6 different locations throughout Japan and the rest of the world, so it's very hard to make sure everyone uses everything correctly.

I would like some users assigned to a specific role to be able to import to specific tables without being a full App admin. The only option in a limited user views seems to be to add a single new record.

I really need an option to make a field required in the form IF a certain checkbox or dropdown is selected / checked when creating/editing the form.

E.G. if a form gets a checkbox in "Cancellation" then the text field "cancellation reason" would become a required field as long as that checkbox has a check at "cancellation".

This seems fairly easy to build with JavaScript, so I hope for this option as it would open up new possibilities!

When will we be able to duplicate apps?

It would be incredibly helpful to have an automatic logout feature so that if a user closes the window without logging off, he/she has to login again. Similarly, a login left unattended for more than a preset time would automatically log out. Thanks for considering!

Provide ability for a user to recover a record that has been previously deleted.

It would be very helpful to modify existing records. But really this is a work around for not having a calculated user field in my case. For example.. if I am using TrackVia to dispatch people... I need a way to unassign it at the end of the day if the record is not signed off (ie a condition is not met)

I would like to see a "tighter" layout of Forms. Currently, I feel the fields are too large with the font size, in-field padding, and the field-to-field padding.
If we had the ability to reduce the size of the fields and padding, the presentation wouldn't look so large with alot of wasted screen real estate, plus we could potentially squeeze in 5 or 6 columns wide.
Thanks!

Classic introduced the idea that a record could be linked via computed value (when first created). Linking a child record to the host of parents that are often logically connected is prone to error, but more importantly is something my users aren't willing to do.

For example, if I link a Support ticket to a Contact, it makes sense that the Ticket would link, in turn, to that Contact's parent Account - without the user having to enter the information. You were almost there on this feature in Classic - why is it absent here?

No matter how you think about it, RADIO BUTTONS are 100 times faster to click on than choosing something in a dropdown menu!

Another REALLY EASY to implement improvement, and LOTS OF PRODUCTIVITY for everyone!

I would make it as on option to "show a dropdown menu as radio buttons".