Repeating groups: combining information of different types

Hi there!

I am looking for your help while setting up a repeating group list that tries to draw in information from two different types.

I have one data type called Projects and the generic data type Users. In Projects, I do not have my users’ names - just the unique IDs which correspond to the unique IDs in the Users data type.

Now, I am trying to set up a repeating group predominantly showing projects (so Type of content is, of course, projects), but I also try to draw the clear text names of the people associated with the projects into that list.

I have tried:

  • Simply adding a text box with dynamic content in which I search for Users, constrain the unique id to the Current cell’s Project’s id - that does not show any text.

  • Adding a group of type “User” and placing a text box referencing the User’s field “First Name” with dynamic content - that does not show any text.

  • Adding a repeating group of type “User”, searching the type “User”, configuring a constraint to the matching of both unique IDs and placing a text box referencing the User’s field “First Name” with dynamic content - that does not show any text.

This does not seem to work: none of these approaches show me any information that I am trying to look up in my Users data type based on the uniqueID in my Projects data type.

I am sure this is a basic question and that I must be doing something obvious wrong here. But I cannot seem to figure it out. I have googled for some time now and am at the end of my wits. Could you give me a hint?

Thank you for your help!

No, you don’t… (or if you do, that’s not the right way to do things in Bubble)…

You should have a User field on the Project datatype - probably that’s what you’ve already got, and you’re just thinking about the wrong way - but if you don’t, then that’s what you need to do.

In any case, to find projects belonging to the current User (assuming that’s what you’re trying to do) just do a search for products whose User is the Current User.

Note: all Things in Bubble have a built-in User field called Created by - which denotes which User created the thing in the database. Often you can simply use that field for what you’re trying to do - although depending on your app, that may not be applicable (personally, I rarely use the created by field for this anyway - it’s often better to add your own User field no matter what).


I was trying to

  • separate unique identifiers from more decorative attributes (e.g., names, titles, etc)
  • work with unique identifiers and draw in attributes if I need them
  • not keep multiple records of the same thing

I have my users’ names in the User data type. But I need it in context of Projects, Transactions, Messaging, etc. Do I need to save a copy of my users’ names to every other data type as well? I sure hope not. My database would shoot up in size. At the same time, I am reading that many developers here are very efficiency-minded.

Maybe I am thinking about it wrong?

Thanks for your thoughts!

But I don’t only have Projects, but also Transactions, Messages, Teams, and a number of other data types. It can’t be that I really need to save a copy of the clear text name information - which is three fields: title, first, last - in each of the other data types, right?

Conversely - would I then have to write my project titles also to the User data type to make sure that if I am trying to do a User repeating group to also have access to their projects?

No, what I am trying to do is simply list all Project titles next to their User name. A simple list. Problem being, I only have the unique ID of the user and the User’s name only in the User’s data type. It seems intuitive to simply search for the User by unique ID associated with the project and return the name from the User data type.

…on second thought, I think I understood now what you said. I’ll try that at once! Thank you! :slight_smile:

That’s precisely what you don’t need to do…

That’s why you need to have a User field on the various other data types to link them directly to the User.


Thank you very much, Adam! It turns out I did not read your text close enough. I keep forgetting that I can define types to contain other types… Sorry and thanks for helping me Bubble greenhorn! :slight_smile:

1 Like

Thank you very much, Nigel! Just as with Adam below, I misread the User type as “name”. Fully understand now. Thanks for helping a Bubble greenhorn! :slight_smile:


@adamhholmes @NigelG

Thanks again, guys - you helped me a great deal by reminding me of the data structure in Bubble!

To finish this thread up: I tried it and failed again. Until I realized that the User data type is privacy protected. That was the reason why I could not get any names out of that data type by “digging deep” through a User-type field in my projects table.

I suppose keeping the User data type private is a good idea. This means that I shall create a secondary table with everyone who “wants to be found” and with the information they want to be found with.

Would you recommend keeping the Users data type as bare-bones as possible and almost immediately adding a second list of users if the app’s aim is also to provide overviews on what everyone is working on (i.e. much is won from transparency)?

Can’t you just set up your User Privacy rules according to what you need? Rather than creating a separate datatype?

Good point. I have to explore that part of Bubble more thoroughly.

Seems that I even did that at some point since the documentation states that out of the box, “User” is not protected by any rules. Must have set it up and forgotten about it somehow. Of course, that does not make helping newbies any easier… :confused:

Thanks again - learning step by step over here! :slight_smile:

Ahaaa - good to know! I was already doubting my memory. But it makes sense that the instructional videos cannot be update with every little change. Thanks for mentioning this to me!

Good idea about the “is public” field! I think for the time being, I will sideline the topic of privacy for a while until I have reached a consistent idea of the structure of the app. Setting things up wonky just costs too much time in troubleshooting my way around some privacy settings I don’t need now - but will need to look into in depth a little later.

Thanks for the pointer in any case - you guys are extremely helpful! :slight_smile: