Don’t see a feature request for this although mentioned in community so just adding here to so I can get feedback.
At the moment I’m currently building out my Softr Database structure and have everything in one database because most items in my database (invoices, actions, contracts, risks, purchase orders etc) need linked to a project ID or a client etc which I have a tables for in the database.
It’s starting to get a bit messy with all the tables I now have and with the 200,000 limit on records in the database for business plan, it won’t be long before I reach this limit if I carry on building everything in one database.
It would be cleaner and easier to manage if we could have multiple databases that could be linked across. So I could create a database for Resources (Users, Clients, Projects etc) and then create related records from other databases
Alternatively having an option to sync certain tables across databases would work too.
Hi @sarah_h Totally agree! I’ve brought this up in the past, and if I recall correctly, I believe Softr will be implementing linking across databases, although there is no timeframe that I am aware. The 200,000 records per database is very limiting, and to your point makes it necessary to contain everything in one database which can get messy quickly. Fingers crossed Softr rolls out an update for this. They allow 1,000,000 records across all databases, I think they should get rid of the 200,000 cap per database and let us utilize the 1,000,000 across our Workspace - whether it’s in one database or multiple.
Yes I originally started moving to Softr DB because the limit on my account was 1,000,000 records across the databases but only recently realised the 200,000 limit per database which has put a hold on things for now until I get a clearer picture of how this will be managed going forward. Either remove the per DB limit or allow cross database linking. Hoping this is something that is looked at soon. I’m kind of in limbo at the moment between 2 systems with no clear path of where to go @artur@Jjenglert can you provide any input on this please?
So I’ve been playing around with Make.com as I have a subscription already in place (I’m not a very advanced user of it) but I think I can look to create Project ID and Client tables in multiple Softr databases then every time a new record is added in one database it updates it in another through the automation. Not sure if this is good practice or not but might be a workaround for now. The automations in Make for Softr only seem to work on a schedule rather than watching the table and triggering as ‘immediately as data arrives’ which is an option I have for my other Scenarios which use SmartSuite as the trigger. Anyone doing something similar? Any feedback on this method?
for instant triggers on make the provider have to use webhooks which the scenario catches. hope they update it with softr workflow, that you can trigger on specific changes like airtable automations. @sarah_h
Ah ok, so it’s not something I’m doing wrong, it’s just not available functionality with the way it’s connected in Make. I’m patiently waiting for Softr Workflows and hoping this will help with some of the issues I’m facing. In the meantime I’m just trying to find ways to make things work so we can properly start using the apps I’m building
Yes I started building out everything in a single DB but it was a lot of tables and was becoming difficult to manage so I then created separate databases for project management, operations, cost control etc. but these all need to link back to Project IDs, Clients etc. which I can’t currently do. I’m now unsure what’s the best plan going forward. Should I go back to a single DB or continue with separate and wait on a sync function or linking across DB (so I would have a Projects and Clients table in all DBs)?
There’s also the 200,000 record limit for a single DB which we’d hit quickly if only one DB used
@artur ok thanks I’ll will revert to a single DB. Do you know what the pricing is for over 200,000 records in a DB? Or who is best to contact regarding this?
Hi @sarah_h I had the same question about pricing. I have a client on the Business plan. I wanted to make sure they have room to grow, as the database record limits could be restrictive. I requested a quote for 1,000,000 DB records and the price was over $1,700/mo (I’m in Canada so it’s closer to $2,400/mo. for us). This is because Softr forces you to upgrade to the Enterprise plan. This has been one of the biggest disappointments about Softr so far. They include a 1,000,000 records per account but they won’t let you effectively utilize them because each DB is restricted to 200,000 records, and they don’t allow linking DB’s. @artur something needs to be done about this. This has been my biggest red flag since transitioning to Softr. It’s clearly price gouging as there is no justifiable reason for this type of price increase.
We need a simple way to add additional records for a reasonable price, without being forced to upgrade to the Enterprise plan.
Agreed that is an excessive amount. We wouldn’t be looking to go over the 1,000,000 record total but need it within 1 database not across databases. Given that the Business Plan is $269/month we need something scalable for increase in records
Ok, I see i’m not the only one confused by Softr pricing. Whats the point of a 1,000,000 records limit if each database is limited to 200,000 records and there’s no ability to connect databases? 800,000 useable records gone to waste. Softr, please fix or explain the rationale behind this.
Agreed! This is something Softr needs to address. I’d like it if Softr simplified things and allowed us to use 1,000,000 records within a workspace as we see fit. Could be for one project or split across multiple projects. The ability to link records between databases would also be great.
