I'm trying to build a Retool application that connects to a PostgreSQL database and allows users to perform full CRUD operations (Create, Read, Update, Delete) on the data. I want to present the data in a spreadsheet-like interface, similar to a grid or table component.
I found a YouTube tutorial that seemed to address this, but it's outdated and no longer works with the current version of Retool. I've also been researching and have found some individual resources for specific CRUD operations:
However, I'm still struggling to integrate these into a single, cohesive CRUD application. I've spent several hours trying to piece things together, but I've encountered errors.
I came across a similar forum post, but the user there also faced a lot of errors.
My specific questions are:
Does Retool have any up-to-date, comprehensive documentation, tutorials, or videos that specifically cover creating a PostgreSQL-backed CRUD application with a spreadsheet-like interface?
If the answer to the first question is No, current basic approach is to continue searching through similar forum threads, addressing errors one by one, and trying to build the application incrementally? (I understand that debugging is inherent to engineering, but I'm concerned that this approach might be very time-consuming for something as fundamental as CRUD operations, and I'm hoping there might be a more efficient path...)
Retool recenty launched Retool University but going through the modules they explain how to set up your queries and so on. They don't go into detail on how to create a spreadsheet-like interface. I haven't seen anything very detailed on this.
I think you could layout the functionalities that you want to achieve in a post (before starting to build) and the forum members will be able to guide you on the best approaches to take.
With regards to building a spread-sheet like interface. There are many rabbit holes you could go into (see recent example here regarding "undoing" things), but it all boils down into what are the "non-negotiable" functionalities you want to achieve, and those you could change to a more "Retool approach". I understand the need of replicating what a business already has in a spreadsheet, but sometimes I've seen that when I present my clients other options that make the work more consistent, they understand it and accept the change.
Thank you for sharing. I understand that it is not something that I can easily make.
I was able to build what I needed, though.
For those who haven't used Retool before, let's set some expectations:
Retool isn't something you can just pick up and use instantly. It requires some time investment to understand its intricacies. Accept that it has a steep learning curve. You won't be able to figure it out without an effort.
You'll need to rely heavily on resources like past forum discussions and video tutorials (but some of them are out-dated), and be prepared for a lot of trial and error. If you're new to the platform, don't expect to build something in just an hour or two.
You will get stuck – it's part of the process. Therefore, carefully consider whether the functionality you're aiming for is truly essential."
You're absolutely right Tom, and what you said it is not said enough. There is a steep learning curve. Every 6 months I take a look at the apps I made then, and there are many things I wouldn't repeat or I would do different. And this has been consistent over the years. So, really appreciate you sharing this.
On the other hand, I feel really pleased that my you tube videos have helped you! Do send me a DM if you think there are other videos for beginners that would make life easier!
Wow, I didn't realize you were the one who made those videos I was watching! What a surprise. I wanted to thank you because your videos were extremely helpful.