My pleasure!
Bubble can definitely search accross different data types, but the data source must match the type of content of the RG.
For example, let’s say you have two types: “User” and “Card”.
Each User can have many cards, and be on the lookout for many “Cards” and each “Card” can be owned or requested by many Users.
With that type of app, your data structure setup could be:
User
Fields
“Owned Cards” (type: Card, list: yes) – the Cards this User has
“Requested Cards” (type: Card, list: yes) – the Cards the User is looking for
“Last location” (type: Geographic address, list: no) – the User’s most recent location
“Trades” (type: Trade, list: yes) – the Trades a User has been a part of
Card
“Name” (type: text, list: no) – the name of the Card
“Owner Users” (type: User, list: yes) – the Users who own this Card
“Requested by Users” (type: User, list: yes) – the Users who need this Card
“Trades” (type: Trade, list: yes) – the Trades made for this Card
Trade (or Transaction)
Card 1 Trader (type: User, list: no) – the first User
Card 1 (type: Card, list: no) – the Card the first User is trading
Card 2 Trader (type: User, list: no) – the second User
Card 2 (type: Card, list: no) – the Card the second User is trading
Date of Transaction (type: date, list: no) – the date of the trade
Location of Transaction (type: geographic address, list: no) – the location where the trade was
This data structure would be pretty flexible for querying. If you’re needing to find other Users who have the card(s) that the Current User is requesting, and who are within 0.5km of the Current User, the search could be:
Type of Content: Card
Do A Search for Users’s Owned Cards
User Constraint search:
- Last location is within 0.5km of the Current User’s Last Location
Intersected with
Current User’s Requested Cards
The results of the repeating group would show you a list of Cards. Then, you could add another repeating group in the first cell of that repeating group which is:
“Owned by Users”. That inside repeating group type would be “User”, and the data source would be “Current cell Card’s Owner Users:filtered (constraint, last location is within 0.5km of the Current User’s location)”.
This way, you’d be shown a list of Cards that the Current User is looking for, and a list of all of the Users who own that Card, within 0.5 miles of the Current User’s last location. Is that similar to your app’s setup? 