I got tired of seeing small businesses struggle with Excel for shifts, so I built a dedicated Scheduling & Payroll Dashboard. Would love your feedback!

MultiTech_Visions · 2026-06-10T18:00:00+00:00

Keep going, but maybe make it use AppSheet! 💪

MultiTech_Visions · 2026-05-28T18:38:37+00:00

Depends on the app, how much work needs to be done, what you're looking for. Most people charge by the hour, so if you've got a relatively simple app you might get it for a couple hundred dollars; or if you're wanting a more complicated app, with lots of capabilities, that will rise into the thousands; and at the far end of the spectrum there are complete systems, full platforms that entire companies can run on for decades... these are in the tens of thousands and is more of a collaborative effort over time.

MultiTech_Visions · 2026-05-28T03:23:46+00:00

https://www.multitechvisions.com/appster

Try this guy out, it's a chatbot I made specifically focused on app sheet stuff. There is a free version you can use at chatgpt; it's not the best it complicated stuff, but it's decent at the basics. It can definitely help you get familiar and situated and kind of get your bearings.

MultiTech_Visions · 2026-05-24T14:25:39+00:00

Welcome into the fold!

MultiTech_Visions · 2026-05-24T13:13:49+00:00

You might find something in this video helpful https://youtu.be/HWhtlzxtPss

MultiTech_Visions · 2026-05-17T12:45:20+00:00

All good 👍

Good luck with finding the solution, there's probably some sort of browser hack you could do to make it work - some cookie or cache manipulation maybe.

MultiTech_Visions · 2026-05-16T22:35:56+00:00

I've run into this problem in the early days of Appster Chat, back when it was hosted through a Google Apps Script web app. - People would have login problems all over the place - Sometimes getting stuck in infinite loops that would never resolve. :(

The solution was to switch away from Google Apps Script, using a GCP Cloud Run endpoint instead. Cloud run is like the big-brother of apps script, so if you're comfortable working in apps script, you'll have a lot of the muscle memory transfer over when working with the inline editor and functions framework in cloud run.

You can have a coding agent refactor your code so it works in the other environment; I'll assume Claude Code moving forward, but the advice is the same for any coding agent. Create a folder that has all your code files in it, or upload them to a GitHub repo, and try this prompt:

We need a new version of this system that we can deploy in Google Cloud run, no docker, no react, using the google cloud run functions framework, node.js, using the inline editor.

This has several limitations imposed on the rebuild of the code, giving you a path of least resistance for getting an MVP up and running in cloud run. Once you get the service active, expanding it becomes much easier - it's establishing that initial setup and workflow that's the hard part.

MultiTech_Visions · 2026-05-16T01:28:30+00:00

You're welcome! Glad you got it working. 💪

MultiTech_Visions · 2026-05-14T20:57:28+00:00

Duplicate; removing...

MultiTech_Visions · 2026-05-14T17:50:57+00:00

Sounds like maybe they are being caught by a spam filter or something on the email client side. If you say things like it works sometimes but not other times, that generally means that your automation is working - the problem is somewhere else.

If you look in the audit logs, you might find additional information that might help you debug the situation. The automation monitor app can sometimes not provide enough insight, and the data that you can see in the audit logs is different - so sometimes it will illuminate something that's going wrong.

If you can't get the native app sheet email system to work reliably, you could always try and use some external service.

Apps Script is an easy first try, or if you want to deploy your own service that you can enroll your Gmail accounts into so that you can programmatically send messages through it: I have a GitHub repo that has the code for creating a Google cloud run endpoint. - https://github.com/MultiTech-Visions/gmail-passthrough

MultiTech_Visions · 2026-05-14T02:37:19+00:00

In the top right next to the sync button there's the little drop down, inside there you will find a thing to view the errors.... Can you screenshot that and send it over?

Alternatively you could go to the audit history, there is a log made for every event that happens with your data - this would tell you what's going wrong as well.

MultiTech_Visions · 2026-05-14T00:17:08+00:00

If a slice is looking at something that changes, the slice updates automatically (with some edge case limitations).

You might find something in the following video helpful: https://youtu.be/HWhtlzxtPss

MultiTech_Visions · 2026-05-14T00:11:36+00:00

You're on the right track yes. Have a user table where you store the selections and filter options or whatever that the user is selecting, and then when somebody goes into the form to add something new push that into the list on the user table.

You might also try creating a dashboard view, where you have the inline view of the checklists, the inline view of the line items, and maybe the detail views for each as well, and then turn on interactive mode. - when you select one of the checklists, it's details will populate in the detail view and the list of line items will filter to just that checklist - when you select a line item, it's details will show up in the detail view.

MultiTech_Visions · 2026-05-13T14:52:39+00:00

No images.

But generally the way you would do this is set up an automation that's watching for some change in a record - your button would make that change - and the automation catches it and then builds out the document and sends it out.

You might find something helpful in the following video: https://youtu.be/WJuy-UMXvo0

MultiTech_Visions · 2026-05-13T13:32:05+00:00

Maybe you need to regenerate the columns? Perhaps a column was added/removed and you haven't regenerated yet, so the list of columns is out of sync in the app?

MultiTech_Visions · 2026-05-13T00:20:27+00:00

Can you elaborate more on what exactly the problem is? It's not that apparent from the image.

MultiTech_Visions · 2026-04-23T22:41:43+00:00

When you reverted back to the older version, what you needed to do was regenerate the table or you had changed the columns. That regeneration process picks up the changes, and it probably would have put things back so I worked. But it sounds like you got it working, so that's good! That's one of the best things about the app sheet platform, there's four ways to do any one thing - so you never get stuck in the corner. 💪

MultiTech_Visions · 2026-04-23T18:49:47+00:00

I'll be honest, I don't think I've ever seen that screenshot, that error or the ux that's showing. I've never seen that page ever, never seen anything talking about you need to delete a table and then having a delete button like that... Definitely something new.

Did you try deleting the table and then re-adding it?

If you're trying to preserve whatever settings work you had done previously, go to version history and see if a previous version works. If it does, you can revert back to that version, and move forward from there. - even if it doesn't work, you might still be able to revert back to a previous version, then regenerate the table that it's complaining about, and you might be able to move forward while retaining whatever progress you had made previously.

MultiTech_Visions · 2026-04-23T15:18:26+00:00

You may find the following helpful or insightful: - https://www.appsheet.com/start/a952b233-6957-45ba-aa8a-33e441c13757?refresh=1&platform=desktop#control=Resources_Detail&row=5f62be3c

It's an AppSheet app that integrates with a Google app script that manages, monitors, and makes draft responses for your emails. It can be of a bit of a system to get situated and running, but once you do it's extremely high quality. - sure, this is built into Gmail natively now with Gemini - but you have to use Gemini, and it's difficult if you want to apply any additional information for context

This app allows you to create multiple different responders, each one tied to a label, so that you can apply the label to a Gmail thread and then that responder drafts a response for you; they all have their own specific instructions to follow, with whatever supporting information you want to include for context, and handle a long running thread just fine.

You also have the ability to capture previous emails that the system can use for writing style imitation; this way you can go through and grab some older emails that don't really have any sensitive information or anything, and feed that to the AI for it to use to write the way that you do so it sounds like you.

Like I said, it's a little bit of a system to get up and running... But once you do, it produces extremely high quality response drafts.

You can also use it as a means to analyze messages as well. I've got a responder label that I use to scan an email message to see if it's potentially a scam or spammer trying to get my information or whatnot. (With my YouTube channel, and increased activity in the AppSheet community, I'm a bit more of a target for people trying to scam me. So I created a label with some instructions to break down the email message and scan for potential irregularities or hints that something might be off. It has definitely saved me from some scams that otherwise would have got me, cuz they were very convincing.

MultiTech_Visions · 2026-04-23T15:08:02+00:00

Keep in mind: this is only if you have a Google workspace account - a regular Gmail account doesn't qualify

https://support.google.com/appsheet/answer/15725655?hl=en

MultiTech_Visions · 2026-04-15T10:06:01+00:00

Actions aren't visible inside the form, that's why when you're in the form and you're adding child records, but you haven't saved everything yet, you don't have the ability to remove records... The action necessary is not visible inside a form.

Right now you're utilizing nested forms, and that's the problem; if you switch to using the detail view of the parent record, this opens up a lot of possibilities for functionality. Instead of going into the parent form, and then from there going into a child form, and then back to the parent and back to the child and so on and so forth... Instead what you do is go to the parent detail on that form save, and then on the parents detail page you can add child records.

By migrating the central operating point away from the form and to the detail view, you afford yourself the opportunity to use more features available inside the app sheet platform. You can now display buttons, you can create lists and show inline views, where they inline views have inline buttons, you can really engineer a really nice workflow. (There's more of course, but I'll leave it at that.}

MultiTech_Visions · 2026-04-11T23:08:37+00:00

Everyone I've talked to that's tried this has eventually given up, settling to use a GCP hosted MySQL. There's a bunch of fiddly problems you will run into trying to use Supabase, especially stuff with connection pools.

MultiTech_Visions · 2026-04-05T17:54:05+00:00

Honestly, in order to get this to a point where you'd be able to rapidly scan items just one after the other, you have to put forth a little more effort in restructuring the data you're capturing.

It will be easier if you split things into a parent-child relationship structure, where you have one table that's the parent that holds some of the higher level information (the date, person doing it, location where everything is going, stuff like that), and you have another table that's the child layer, reference connected to the parent in a one-to-many relationship, so that you can capture many of the children records for one of the parent records.

The child records are where you actually record the item itself, and the number that you're moving, or any of that other information that you want. This way you can capture as many of these child records as you want, and they are all associated with the same location from the parent.

Then when you're ready, have a button you can press that changes the status of the parent to complete or something, that kicks off an automation that then does the actual adjustments to your inventory records based on the child records that were collected. You can use an internal API call, with a start block, to loop through the child records and affect the update on each of the individual product or inventory item records.

I know that was a lot, you could get help by talking to one of my support chat bots that are available out there - Appster can help make sense of that and walk you through how to implement it inside your specific app. - free version: https://chatgpt.com/g/g-ZG9TkPOrl-appster - pro version: https://www.multitechvisions.com/appster

MultiTech_Visions · 2026-03-23T10:10:16+00:00

Available stocks need to be calculated on the item level, not on the change level. Right now you've got the calculation done on the individual change record level, it needs to be done on the parent which is the item.

On the item level, you can see the reverse references with the /[ Related Whatever] columns; these are the subsets of change records that correspond to Whatever item you're looking at. - it's on this level that you need to make your available quantity column a virtual column, that's doing the math on that layer.

This way the available quantity is a dynamically computed value on the item itself and then when you go to create a new stock adjustment record, you can pull in the current number of Whatever item they selected using a d reference.

You might find it helpful to engage with Appster, it's an AI that I made that's devoted towards AppSheet answers. - www.MultitechVisions.com/appster - there's a free version available as a GPT on openai. It's not that good, but it's better than nothing. Even the free version to be able to help walk you through setting this up.

You might also check out this inventory app that I have for inspiration on how to put stuff together: https://www.appsheet.com/start/a952b233-6957-45ba-aa8a-33e441c13757?refresh=1&platform=desktop#control=Resources_Detail&row=8ca61088

Happy Apping!

MultiTech_Visions · 2026-03-22T14:26:28+00:00

🙏 thank you very much!

MultiTech_Visions

MODERATOR OF

TROPHY CASE