Problems linking data to create/view profiles for different user types

Hello, I am hoping I can get some help with setting this up. For My app, I would like to have three different types of users each with its own type of profile information. As I have it set up now I have 4 different databases; one for users, one for Type1, one for Type2, and one for Type3. Right now I am just focusing on user Type1 because I am assuming that the process will be the same or at least very similar for the other two user types. The problem that I am running into right now is relaying the data between the sign-up, creating the Type1 profile, and then displaying that information.

As I have it right now I have one screen that allows the user to select what type of user they are. After selecting their user type they move to a screen that allows them to sign up, when they click sign-up it creates a user and a Type1 profile and links to the next screen which is a form to fill in the profile information for the Type1 user. Clicking the submit button on this screen should update the profile and links them to a home page that should display the information they entered for their profile.
Hopefully, this diagram helps explain what I am after.

Right now after the user fills in their profile nothing shows up on the “home” page even with using the smart text. I think that this is because there is not anything listed under the available data section, but I’m not sure how else to force that to link up because the form to get that information has a link directly to this page. I would also like to give the user the option to go back and edit their profile information but that’s kinda a second step, first step is to have the info filled out and show up.

Any advice or help is greatly appreciated, Thank you!

ETA: Right now I am just looking at each type being able to see their own profile data. For example, if I am a type one user I want to fill out the profile and see what it was that I filled out, right now I am not looking to see anything for the other types. Eventually, I will want to see the other profiles for the other types but I’m not there yet :slight_smile:

Hi @Oneil93 " I’m a big fan of stargate so i’ll try to help you as much as i can"

1st thing: you don’t need a collection for each type, you just need to put a boolean value (true/false) property to users (ei: IsEmployer, IsCandidat, IsEducator) those are just examples you can put whatever you want,

2nd, after choosing the type and clicking and going to the right screen you can add an action to the signup button (update logged-in user) and you set the property (if he’s en the employer screen set the value IsEmployer=true)
---- 2nd BIS: you can do this in one signup screen if you don’t mind using one background color

3rd: after setting the right true/false property for the users, you can use the same home page to display information according to the profile type , you can filter everything according to IsEmployer = True for example

here you go, I hope that’ll help you, good luck

Thanks for the help! I did include a boolean value for the different types like you described in your first point but then used that as the indicator to direct the user to the type they chose.

Could the method that you are describing in your second point still be used while having different properties that belong to the different types of users? That was my logic behind having a collection for each user type. Like an employer would have information that would be applicable to them but not to candidates. For example, an employer would have an industry and company size but a candidate would not.

Yes totally, you can put all the needed fields in your users collection, and display only whats proper to the type,
common fileds: Name, email, Phone
employer: company, number of employees, etc…
educator: has degree of, past experience, field of expertise…

on adalo you can put any fild you want, give it the visibility you want and the value you want,
you’ll just have to make sure that the right data source is available on the screen

PS: (that’s why you shouldn’t have multiple collections for every type, because users data is available on all the screens )

That worked perfect! Thank you, I was afraid of loading down the users file too much by having information from each type in it, but if it works that makes me happy!

That’s great, I’m happy to help, good luck with your app

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.