By supporting map views in flows you could select a location from a map; Currently there is a lot of click through to select a parent then a child, then perhaps even a grandchild. It would be nice if i could specify with a view task that i want to be taken to a child view instead of a form(that i am forced to edit) and then a child view.

I don think this will be a priority, but allowing a flow to trigger an app script to open a view with certain quick filters applied would be a really cool and helpful feature. i have an idea for a reporting system, but it requires building numerous views with filters. If certain choices could be funneled into a quick filter it would be like a custom view creator and keep people from getting lost in creating their own quick filters.

For the text box widget:
- please increase character limit from 255
- formatting such as bold, underline, italic, color etc.

Dates are currently exported in 'MMM dd, yyyy' format (e.g. 'May 21, 2017'), which adds an extra few unneeded steps to re-format date fields when re-importing, as date fields must be imported in 'yyyy-mm-dd' format (e.g. '2017-05-21).

Is there a limitation to the amount of show/hide options on a form?
Once I entered my last batch of fields the show/hide is no longer working and the only fields I see on the form are those which do not have show/hide configuration.

Fairly simple: Apps Script isn't as useful as it could be without being able to access every field in each table. If you use an auto-counter or triggered field for a record ID, you are currently unable to load that record in an apps script (e.g. using loadrecord(), etc).

It would be very helpful in viewing a table if the column header text would wrap like the record fields. Currently, the column headers are truncated until the user manually drags the column width wider. This creates too much unnecessary work and causes the table to display too much empty space. The user has to continually scroll left and right to view a table. This issue is especially troublesome when a column is grouped or summed, etc. Thank you for your attention to this matter!

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 am finding the information on Application Scripts to very limited.
I want to capture currentvalue from a parent table in order to retain historical data, but I am unclear on which type of field to capture this data. ..or even types of fields/data I can pull from. According to the videos, I think that I need something like this:
def x = ["field within current table"]
x = currentvalue["Relationship name to parent"]["field name of parent"]

Am I missing something???

As "default value" for a user field, we can currently only choose from an actual user.
But I'd like the default value to be the "logged in user".

TRACKVIA provides a default view for each table. This happens ONLY in English.
I´d like to have a default view for ALL tables regardless of the language.

When having a graph view, this appears without a tittle. If you apply a filter in the view, and click OK, you lose track of what the view is about. I would like TRACKVIA to provide the titles of the graphs (including the applied filters) so it makes the analysis and graph exporting easier.

When adding numbers to a field, I would like the app to recognize the numeric field and display the numeric keyboard ONLY (the one that appears when you want to make a phone call). This will allow an easier surf in the app and increase the efficiency and user experience.

My app is multi-lingual (5 different languages). Now, I have 5 times as much tables, views and forms (we had to basically develop 5 apps) because TRACKVIA doesn´t support Localization services which are translation services that allow to have only 1 set of tables, views and forms.

In the calculated fields of tables, it would be nice to be able to comment our formulas like you can in programming languages and even in Excel. In Excel, this is done through the N() function. You add the N("Insert Your Text Here") to the end of a formula to be able to go back at a later date and give yourself or your teammates an idea of the logic behind the function. This would be very useful when creating complex if() functions.

Ability to display all Notifications and Share Views created by any user to the Admin (or Super Admins) users. Include an option to mute individual or all notifications and modify/delete notifications and views.

I have created a view and sorted it for a "preferred parent view" on a form. However, in the form, the view is no longer sorted...

Please change the font size, it's way too small. I can't read this stuff!!!!!