Easy way to change App's Datasource

Ask the community
,
1

I need an easy way to change the Datasource of a So􀀁r Applica􀀂on without having to change every block.
Ideally, I want a setup where I can make changes to the Default So􀀁r App and then Delete the other copies of it and create new ones with the updates and have an easy way to connect each to it’s Datasource. Here is a demonstration:

image
image2587×1627 396 KB

1 Like
2

Hey! There is an easy way to clone your apps if you turn them into templates.

You will have to experiment a little bit but… We are willing to try anything just to avoid block remapping

3

Thanks,
I know the templates but it is only good for making the first production release.
If you have to do changes afterwards you will have to edit each production copy.
I am looking for a method where I can update the original app, delete the production copies and make new ones by duplicating it then changing the datasource of each of them to their datasource.
Please see the illaustration diagram in the original post

4

I also dream of the day when I can simply remap my app data source just by altering its base id.

However when I need to clone again the previously cloned app, I would turn this new cloned app into a template itself so I can clone it again and then I don’t have to rely on the first product release changes.

Either way if you point your cloned app to different data sources with a ‘magic wand’ you will have to edit each production copy when changes are needed no matter how you manage to duplicate them.

5

Thanks @acjnas
The template method is useful only when I am making a new setup for a new organization.
The workflow here is different. Let us say I have the template T1 of the app with its Datasource and have a production instance made of it Called AP1 connected to datasource DS1. I made updates to the template T1 and want to

  1. Delete AP1
  2. Use the updated template T1 to create a new application called AP1
  3. Connect the new AP1 to its already existing datasource DS1

The most time cosuming step is Number 3

6

Any update on this? @kelshaer raises an important point when it comes to running a development and production version of an application. Changing each of the blocks (100s) manually is not practical. Not that there is no changes to table names, just the data source, eg changing one Airtable base to another. All other mappings preserved.

1 Like
7

Did anyone find a solution for this? I want to be able to create a demo of the app with placeholder data (Airtable base of made up info) but can’t easily unlink the copy of the Softr app from the original Airtable base. SO frustrating!

8

If the schema is the same we will add such a feature… don’t know the timing but something good to add

2 Likes
9

if you mean the image above, yes! creating a copy of my Softr and easily changing the data source – and that would also assume that the new data source (with the same tables, everything the same in Airtable except for the placeholder data) would be connected in Softr in all the pages and blocks where the previous data was connected.

I’d even be willing to manually go through every Softr block to reconnect to the new data source if there was a way to remove the Airtable data source from the Softr copy without deleting the Airtable base entirely.