How is "Field Type" [data type] handled?

You should be able to with text fields (see what I did in your example app)

Yes I see, but how did you do that? It doesn’t work for me when I try to search for the email…

Built in fields won’t work :frowning: I did it by changing the search field to text so that I can search the name field. However… I just tried the unique id (a built-in field) and that does work… Is there a reason we can’t search the built-in email field for a User when working with User field types in App Data?

Yes, we haven’t added that as it wouldn’t really make sense to search on email since the view would at most return one entry. You can use the quick search bar for this.

Gaby, Do you mean you changed the search field to “name” (which is a text field)? That does work for me, but you don’t get email in the linked data, you get name. So I’m not understanding I guess, because I can’t get that email to show up in the linked data type as you did.

Right, that’s what I did in order to select the user, but then in order to display the email in your data view, change it back to email. That search field functions both as the field to search and the field to display.

@emmanuel Is the intended design to not allow linking of data types via number fields?

Sorry, i don’t understand the question.

to not allow linking of data types via number fields

What does that mean?

So I’m trying to link two data types via a field that has a type of “number”. When I search for that field to link, it doesn’t return in the search. Only text fields are able to be searched and linked.

If you can share a link to your app it’d be helpful.

here you go: https://bubble.io/page?name=index&id=materialdesign&tab=tabs-3

Yeah it turns out it’s a limitation of our search autocomplete, we shouldn’t show number fields. We’ll put that on our list, but anything that touches database isn’t a small project.

We found a way to fix it, you can now type a number.

2 Likes

Awesome! I tested it does work! Thank you!

1 Like

I’m struggling with this… I can’t write the data type field value because the input is text and my data field type is Company, not text.

Here’s a more detailed version:
On signup, users create a team and a company. Because I want these fields to be linked in the way you described above, on data type Team I have a field name of Company and a field type of Company. However, because the user enters this information in a signup form the input content format is text. So in my workflow I can’t write to Company because the expression evaluates to text, but the type is Company. Does this make sense?

I also tried this method to write to the Company field in the Teams data type, but it didn’t work.

…
Just checking some assumptions: When the data type’s field type is text, this is not a direct link, and thus the linkage is not complete in some way…? If no, then why bother to use custom field types?