Dear AppSheet Team, allow the same action names if they belong to different tables In our ongoing effort to keep the editor organized, actions are grouped by tables. Additionally, system actions are always the same (add, delete, edit, etc.) and are automatically named by the system based on their context {the table}. However, when we create an action—let's say "update" for one table, and "update" for another table—the system renames the second table's "update" as "update 2" because it assumes there are two actions with the same name. While this makes sense within the context of the same table, it would be helpful to allow identical names for actions across different tables, since actions are understood in their context (just like add, delete, edit). This current behavior forces us to rewrite the table name (even though the action is already organized by table), which seems entirely redundant. For example: For the "customers" table: our actions {customers_update}, system actions {add, delete, edit} For the "works" table: our actions {works_update}, system actions {add, delete, edit} When it could simply be: For the "customers" table: update, add, delete, edit For the "works" table: update, add, delete, edit But this doesn't happen, what happens is this if we try: For the "customers" table: update, add, delete, edit For the "works" table: update 2, add, delete, edit Don't you agree? This would allow the names to focus solely on the purpose of the action, making them shorter, and we wouldn't need to differentiate them by adding redundant information. I appreciate your attention to this matter, as it doesn't seem like a small issue. Thank you in advance! The same goes for bots and format rules Best regards! ... View more

I've been weighing the pros and cons of creating virtual columns with formulas that I then reference in showIf, validIf, and other properties. I've noticed that creating a virtual column as a reusable programming object is very helpful in terms of maintenance and tracking significant changes between saves. By changing the formula in the virtual column, the calculation is modified wherever it's used without having to manually update each instance. However, as the number of virtual columns increases, the calculation for each sync becomes enormous, which can become tedious from a user experience standpoint, especially when there's a lot of data to load (though this might not be as big of an issue for personal apps). To find a middle ground, I came up with the idea of a column type that's neither virtual nor real (an object column). Imagine it like working in Excel, where you create a formula and then reference it instead of typing it out multiple times. Having reusable objects would be great for maintaining our apps without impacting sync performance. How do I think this could be implemented? I imagine that, instead of writing a formula in the ShowIf, ValidIf, etc., field, we could reference the formulas contained in other fields within their properties. For example, let's imagine a case where Column 1 has a ShowIf, and Column 2 has another ShowIf that depends on the first one. Instead of duplicating the formula, we could create an AND() with the ShowIf from the first one without needing to rewrite the formula, simply by referencing the first one's ShowIf. That way, we would have a precomputed expression instead of two separate calculations. This would apply to everything. For example the next expression: AND(          showif.column1,          expression       ) Or like we have a "user settings" we could have an "objects settings" that would allow us to configure system columns that we can access.   ... View more

Dear Dev's Can you improve visual aspect of Tables relationships... it looks terrible. Its handy for app creators to have quick reference what and where.... but if it comes to present to the management.... ... View more

Currently, if we want to change the order of processes in a bot, we have to delete and recreate them in the desired sequence. It would be much more efficient to allow manual reordering using a drag-and-drop system or buttons to move them up/down. This would improve usability and save time when editing complex automations. What do you think? 🚀 ... View more

Hello Appsheet team.  Could you please update the yes/no column type and add an option for it to work as a checkbox. This is one the most wanted features in Appsheet and it doesn't look so hard to be achived.  You guys already have the toggle option in the quick edit button. Please do it.  We users are getting sick of never being listened to. @MultiTech @lizlynch  @Arthur_Rallu  ... View more

Dear AppSheet team, it would be a good idea to add a button to disable bot processes, which would allow for quick testing. I know I can resort to the action and set it to "false" operating condition, but time is important and there are often shared actions, which should not be temporarily cancelled. For this reason, I request the creation of a button to disable steps in BOTs. ... View more

Good day, dear AppSheet team. Today, I'm writing to request an action that allows buttons to be displayed as primary in any view. Specifically, I need a primary button (like "Add") in a table view. This type of action should function like a "trigger" for BOTs, where tapping it would initiate a series of actions that we can define—except that, instead of monitoring changes in tables or calendars, it would be activated by a button. I appreciate your time in reading this. ... View more

Now Appsheet has a relationship diagram like grid bubbles to show the relationship of table, slice, and view. But it seems to be very difficult to images for the user to define the relationship between many tables, column names, and primary or secondary keys. Relationship of tables, slices and views on Appsheet Relationship diagram of tables on Access and Power Query I think the AppSheet team should consider referring relationship diagram from Microsoft Access and Power Query, It is very clear and easy for users to check the column name and connect the primary key and secondary key. Thanks,  ... View more

It would be beneficial if AppSheet allowed references to tables in other databases (if not from different providers, then at least within the same AppSheet Database). ... View more

Often we need to copy a table from another app that contains configurations we use regularly. It would be great to have the option to clone a table (just like we can copy apps) for AppSheet applications, but with the ability to copy all its configurations. This would save us time when setting up 'Show If' or 'Valid If' conditions, changing only what's necessary for each case ... View more

Currently, all AppSheet plans have a restriction allowing only 20 tables per database. This limitation poses a challenge when creating intricate apps with numerous relationships between tables, especially when one prefers to define everything within the database rather than in the app itself. I understand that AppSheet allows the integration of multiple databases within an app. However, having the ability to define everything within a single database is a feature that would significantly enhance the user experience, particularly for those of us with a preference for more traditional, or "old school," approaches. Thanks  ... View more

Automation details (bots) is missing completely from Application Documentation, so the generated document is not reflecting the actual app. Since workflows are not supported anymore, they should be removed from the documentation generator and Automation details should be added. This would help a lot to anybody who needs to generate a searchable doc from app... Regards, Peter ... View more

Similar to how ENCODEURL() encodes characters to be able to be used on context where HTML values could break the code, we need ENCODEJSON() so that we don't need to manually do it inside JSON body templates on webhooks. It's a pain to check for this manually eventhough I use VSCode to transform to a JSON String. BUT! What if your content is generated dynamically with expressions and you also need that content to be encoded? ... View more

I've been thinking that, like Excel, Access, and many others, AppSheet could have software where the design experience is faster in terms of syncing, and when ready, there's the possibility to sync everything at once with the online version. This is just to speed up the design process. Another great option would be to create a mobile editor so people can edit and create apps while on the go. Best regards. ... View more

The option to capture audio directly from the appsheet. This functionality would be extremely useful for those who need to record voice notes. AppSheet currently does not provide a built-in audio recording feature. While users can record audio files, a native recording capability would be far more useful and efficient. Here are some possible advantages of integrating voice recording to AppSheet. Improved data capturing for tasks such as reporting concerns, gathering feedback, and conducting surveys. Improved accessibility for users who prefer voice input than typing. Improved user experience by streamlining the data collection procedure. I recognise that this could be a difficult feature to implement. However, I believe it will tremendously benefit many AppSheet users. I look forward to hearing your thoughts on the possibility of adding voice recording functionality to AppSheet in the future. ... View more

Although it has not been implemented 100%, we know this will happen; it is just a matter of time. My idea is based on having AppSheet create a system with Artificial Intelligence (Gemini IADoctor), like a nano-worm that enters the veins to cure a disease. When introduced into a user-created application, this Gemini IADoctor would optimize it by removing unnecessary columns, improving expressions, actions, and bots. This Gemini IADoctor should interpret the app, understand the objective and the result, and see what can be done without altering the nature of the application (i.e., without changing it), just as if it were a performance evaluation (but one that can do something about it). This would allow AppSheet and its services to significantly reduce traffic since optimized applications, I believe, are not only better for users but also consume fewer resources. ... View more

Hello community, today I bring you a nice idea for our editor. It would be very good if several tables could be regenerated at the same time in the same process, it would greatly reduce production time. It could be a kind of selection box and, once selected, the button to regenerate selected structures is pressed.  Another option would be a self-detection, tables that must be regenerated due to a change in the database, are regenerated. In other words, make it not just a table action but something at the application level as well.  It would be nice to be able to add, anyway the setting of "whether it is read-only or not" is later. That's all I hope one day we will have that feature ... View more

AppSheet has no reason to become self-absorbed like other platforms do. AppSheet is from Google and as a strategy you must understand that it is a platform that gives people freedom and accelerates development time more than any platform in the world. Therefore, instead of creating your own AI, why don't you try to integrate with Gemini and vice versa? Artificial intelligences learn from iterations and interactions, why not make it available to everyone? ... View more

Hi All, It's all in the title, a possibility to add attachements to the Dynamic emails would be a great addition. Here's my use case. An expense report containing multiple REceipts from an unlimited number of child records, and the Expense report itself as a PDF. ... View more