Duplicated Pages with Database connections: Replace DB to a other DB with same Shema

We offer Pages for some of USER/customer (1) DB contents management…
if we have A other USER/customer(2) who want exactly same management profile with his own contents.
We duplicate page of USER/customer (1) but we need to connect NEW Database contents with exactly same shema for USER/customer(2).

If we have A LOT and MANY inputs+text values connections in this page, actually we need to RECONNECT all of them one by one to the NEW DB for USER/customer(2).

It could be very more Simple to click on #dataset and replace DB to other, with same sheme of corse, and keep all connections in the page ALIVE and never broke connections.

Need comments of all if I’m clear about, if so, I am the only one who need to perform this ?

1 Like

Hey Ron,

Thanks for your question. Unfortunately, when you change collection in Dataset, we drop all connections as there can be so many unexpected things. For example, your field could have the same names and keys, but different types. On the other hand, I see how this could speed up your work.

Either way, this request is not frequent, so I can’t promise that we’re going to improve it in the nearest future.

Hi Adas,
Thanks for answering…
I understand! But Types is not a problem and they are easy to manage! For Us it is a huge work and a real puzzles to reconnect all connections, and check all Filtering and sorting conditions for each of our dataset + settled permission required for each.

For each user we use 4 Webpages data entries tool and 4 to 5 Db are required for good working… We tried and do our best to minimize required Db amount… Why I previously ask also Folders to classified all our Database. We only have folders for members & Stores Db.

All these Filters + sorting is really important according our pages good working coding . Some of our pages have more than 3000 code lines and impossible to put values in dropdowns values connections via coding (So manual connections are required for drops) . It could be easier and faster to change only #dataset coding text by find and replace functions, and in this way will have less chances to forget some connections. But in the other way Manual connections are sometimes easier and better than coding.

Maybe it is not frequent for Now… But Eventually when User will be more comfortable with Db working, they will need it I think.
In the other hand… I don’t think it could be a huge Work for Wix to add this replace DB feature to page dataset… It is not involving lot of conflicts and has no influences with all the rest.
If field(s) is/are not existing with new DB it will just create automatically field [unconfirmed} to be added in Db sheme. A bad understanding of this feature by Users could not have real BAD consequences!

Let me know what you think about!?
And maybe Just talk about it in your next DEV meeting!
If not Will hope LOT of ‘‘like’’ on this post :wink:
thanks!
-Ronny

Could you elaborate a bit about the number of DBs you have? If you have almost identical schemas in each of your collections, why not put data into a single table?

Regarding the need for manual binding, do you have some more cases that coding doesn’t cover besides the dropdowns? Speaking of which, why this (Dropdown - Velo API Reference - Wix.com) is not enough for you?

Thanks for drop options shared link Will check it out seriously… Dev help us to code and always told us It was impossible to code drops values connections

For now we are still developing page coding, we don’t have so much yet… We need 4 Db to 5 db / USer to make work our managing solutions.
So When ready to publish and offer solutions. each User will need 4to5 db + 4 managing web pages + 2 webpages displaying datas for all their Users. display page are easy, problem is managing pages. so if we have 25 Users it could take Up to 100 Database total.

We can’t Put in all same DB : first is the total amount will be a problem but most important each USER need to have their own submitted values and never see the other USERS values. We also need to export some DB to JASON values for a other DESKTOP app. And if JSON code it too heavy (too much characters) it cause problems.

Will post A issue problems we dont’ have before (last week) . Each New Row insert with coding Put our FIELDS TYPE = IMAGE as TEXT value… So our pictures values didn’t save at new Row insert… Make no sense because HEAD field TYPE is settled to IMAGE type… if you have answer about feel free to answer it here Adas…

Thanks!
-Ronny

Thanks for sharing, but I’m still having some hard time understanding the setup. When you say “User”, is it your site visitor, is it some business person that is buying a website creation services? And is 4-5 DB needed per User or per Site?

Regarding your question, is the field key used for inserting images mapped as image field type in Collection?

the answer is : it is some business persons that is buying a Db management services with inputs page tools + some data display pages (like :Head administrator users)… each of these Admin user will have their own visitors users.

About my question : it is the field key TYPE mapped as image field Yes! Waiting about the Site Dev answer to know which modifications he made in the code to solve problem (suppose to be solved but not totally sure… we need to test more). But like I said our coding for this part always worked until this week! You sure WIX do not made any modifications in Submitted images or to fields image type Working ?

Could you send me the link to your site? Will look into it.

Hi Adas, I’m back with this request! Sorry where really busy in coding last few mounths.

This Request would be really appreciated and usefull, specificaly for Tables connections. As soon as Table is disconnected we loose Cells sizing formatting and order VERY VERY VERY annoying and verry long to reconnect and reformat all table cells format.

https://www.cibledetection.com/copy-of-summary-stats-tables
https://www.cibledetection.com/copy-of-3-result-h-g-line-up-clean-1
https://www.cibledetection.com/copy-of-teams-arena-entry
https://www.cibledetection.com/copy-of-1-record-players-list
https://www.cibledetection.com/sparebooking

All these pages need to be eventually duplicated with all same duplicated Database format

Understand we have a big problem to reconnect all when we will need to duplicate!!!

Hi Adas, I’m back to know if it is Wix plan to perform this request ? See following picture. We duplicated this page first, we need to connect MANUALLY all old DB (in Red) to NEW DB (in BLUE). Both DBs have same fields keynames… it is the same 6 DBs for each, many is required according many required FILTERS for each. Once done, we will need to connect manually over than 150 elements in this page and reformat 3 tables from scratch, then will deletye old RED dataset . Make no sense ! Please this feature absolutely need to be implemented!

Hey Ron! What a setup! I’m afraid I don’t have any good news for you. It seems you have quite an advanced case, but we’ll look into it. We might loosen the rules of nuking all the connects upon Dataset collection change.

‘‘We might loosen the rules of nuking all the connects upon Dataset collection change.’’

Yes because if allowed, there’s no possible damage because if field keyName is not existing (or bad field input type), you already have a warning feature with ‘’!‘’ displayed in RED beside item DB connection menu.

And I really think it could be a easy thing to perform for WIX. For tables formatting it will be really more efficient, and this could be helpfull for all you users!

Please Adas, let me know here if you have any new infos about or development. It will be really appreciated! because more than of 6-8 hours/page of work can be done in 15 minutes. We have 5 pages to duplicate in this same way, one of them have more than 200 connections and 10 dataset to be replaced!

Will let you know. By the way, can you share an exemplary site?

@adas-bradauskas Hi! thank you so much, In a previous post here I have shared all Website links. Something else… Is it possible to have more bandwidth from Wix, our pages load is really too much slow… Here some screenshots of 2 pages