Invalid request: parameter validation failed. Chec...

[Daniel_Varela]

I separate data into multiple bases for ease of use, and team-split.
However, I see Interfaces as a way to show data to the client (which could come from multiple bases).
I don’t like having to share multiple Interfaces.
Also, could Interfaces become a little bit as a customer login feature (as softr io allows)?

[Ellen_Wehrman]

+1 to this request - we’re trying to build an Interface that pulls from 3 different bases for one singular audience, and having multiple Interfaces sort of defeats the point.

[Dragos_Burlacu]

Thanks for this suggestion. Will send it along!!

[Sandrine_Coosem]

This would be so helpful! We often have several bases for one client, where the client only needs access to one interface for each base. Right now, that means the client needs several interfaces.

[Rachel_Gartner]

Another vote for this! We use different bases for each customer that we work with, but we’d like to have a single internal interface that shows all of our work for the day.

[Nicole_Hawkesf1]

Another vote for this idea from me, I split bases but interface would be a great way to analyse productivity metrics from data which is currently split across multiple bases.

[Cameron_West]

+1 on this feature as well!

[Jay_Data]

My vote also - hopefully this is introduced soon

[Joanna_Parker]

Just adding our use case and +1. We have bases split by project/department, with syncs set up where they interact, so the team only access the bases/data they need. But our comms team regularly use data points from all departments. An interface that spans bases could mean they only need one interface to refer to, rather than four/five.

[Lise_Rubarth]

You should now be able to sync multiple bases to a new base (e.g., a base for customers) that have multiple bases linking to them. Then create the client interface in this base. I think that this would solve the issue.