Please make it possible to set a limit in minibase filter embed code for the number of minibase records displayed. (Though this can be done globally in the minibase itself, in some locations I want to display fewer records than the minibase settings -- like on a school's front page, for instance, where there's limited space.) In Twitter feed embed code, for example, they use: data-tweet-limit="2". Something like [$APP ID=40253 Limit="3" props="Field1:2019-2020; Field14:116; Field16:n;"$].

Making Minibase fields more responsive. Many websites are viewed on mobile phones, having the input fields fit the view port would really enhance the app.

I would love it for minibases layout to allow responsive design. Very difficult to use our staff directory minibase on a phone or tablet.

It would be great if the styles could be edited to print in a table format when using the custom minibase app. This would eliminate the need to keep multiple files for users to download and print.

Add a restriction to the search to require at least two letters in name for searching. We have had an uptick in spam (in alpha order) and think requiring additional letters could help. Thank you!

Add the ability to add a hyperlink to text in a field.

The functionality of the drop down to descending order in the Minibase when using year or any date information would make ease of use for the end user. Please consider this change. Users are frustrated when looking for the current years Agendas and Minutes.

Free form searches from Minibases should default to "Contains" NOT "Starts With" -- just like Google and all search engines do. (You don't have to type "The" or "A" before a search phrase in Google, for instance... and if you did, you wouldn't know which to do or when it's needed. "Contains" lets you search by any keyword.) This makes it really hard for people to use the minibase search feature, and makes it likely that they don't find what they're looking for.

In Minibase, in particular dropdown menus that are 'dates' such as 'years,' the dropdown should begin with current year (descending order).
Example: https://www.ltisdschools.org/Page/85

When a website user searches a minibase, the filter/search fields disappear after the search results are shown. The search fields should remain visible after the search so that the user can perform another search without having to refresh the page.

It would be nice to have a little more control over the minibase with conditional formatting or fields. ie, something link and if/then type

It would be great if we could have multiple Custom Views from one Minibase
Ex: a table view with 4 columns for the HS while the Elementary needs 6 columns of the data...or we'd like a list view for one school and block of text for another.

Add multiple table styles to choose from for the default table view. Some users do not like the default table style of gray vs. white alternating rows and want a different look, but just need a basic table and don't want to spend the time to do a custom view.

When you do a custom search in minibase and you use the dropdown for the search it automatically displays Starts With. I suggest that we be given the choice for default to be Starts With or Contains. Or make the default Contains. The reason behind this request is that if a person is searching they are probably looking for a string within the search and not the exact beginning of the string. Most searches do not even have Starts With.

Thanks

Looking for the ability to set "Contains" as the default drop down from within the app settings in Minibase. We currently use the minibase to house a lookup tool for seat dedications in our auditorium. Most users are searching based on their last name versus "In honor of James Smith" since they don't remember how the seat name was started. We're looking for them to be able to type "Smith" without having to swap the drop down option each time.

Currently the choice that appears by default when setting "Free Form" as filter type is not select-able.