Turns out this is not a bug…just a poor user experience.
When your primary field for a data type is not set and you have a related data field to that type in another data type, the entry in the database shows as being empty, as in no related entry. What there should be is some kind of information to notify there is a related entry saved, but the primary field used for display purposes is empty in the data type related.
So, I had a primary display set to a company name. On creating a company I am not adding a name, just creating an ID. At the same time I am relating the company data type to the user data type as a data field.
When the primary display was set to company name, the related entry in the user data type showed as empty, like no information was saved.
When I have the above as the primary field, which on the company data type is empty. This is how the database looks to display a related data type
Very clearly “Company” is empty despite the company-id-text being filled. This makes it seem like the related data type did not get saved properly.
When I change the primary display field to the following
Which on creation is created and not empty like the company-name
This is how the related data field looks on the other data type
This clearly shows that the related data type has been saved to the data field properly.
This is a terrible UX design flaw and should be rectified…otherwise other users may feel the same as I do that their data is not getting saved properly.
I don’t know any other bubble representatives tag so @eve this may be a suggestion to pass along.
2 Likes
Forum
Academy
Marketplace
Showcase
Pricing
Features
