Thanks for the reply. It does seem like the simple answer is that Bubble doesn’t do it because Bubble doesn’t do it.
I’ve never been one to not try to understand things that don’t make sense to me, which is the reason for my persistence in trying to get a more technical understanding of what is the difference between a newly created user and a login to existing account. Since Bubble does the mapping of created by for a newly created user, but not a login to existing account, I am very curious as to any technical differences between the two types of users (newly created versus login to existing account).
I’m also never bashful about trying to help push Bubble as a platform to be better, and in my mind it would be better if Bubble were to make it so a login to existing account is treated the same as a newly created account in regards to mapping the created by field.
I’ve also been running into a bunch of headaches with the Bubble API Replace not working properly as per the documentation ( https://manual.bubble.io/core-resources/api/data-api ). In my case I am getting very confusing results with it.
Having a call setup like below results in a confirmation popup indicating the call was sent through properly, but in the database of the other Bubble application, the fields for ‘created-by-api’ and ‘ssn’ are empty and the built in fields are not changed.
If I instead change the setup to not use the query string checkbox, I get an error.
But as per the documentation the Created By field, and the other built in fields which also produce this same error, are all entered as would be in a Get call just like the documentation indicates.
What is more troubling here for me is that when I do not include the built in fields and I have the setup without the query string checked as below, the values of ‘created-by-api’ and ‘ssn’ come through properly.
However, the documentation states any built in fields not sent via a Put call would be deleted, but that is not the case in this situation.
So, I’m having trouble using built in Bubble functions to achieve a simple task of replacing the created by field as workaround to Bubble not treating a login to existing account the same as a newly created account for mapping the created by field.
I know there are other solutions out there that are built by very reliable and trustworthy 3rd party developers, or other workarounds like not using the built in field of ‘created by’ and have a different field related to user, but I try as much as possible to optimize my applications with using only Bubble default features. At this moment it seems like the Bubble default features are not working properly (Put calls for Bubble API) or are not performing as I might expect (use of cookies to map created by to a login of existing account).
When I searched the forum for other suggestions or solutions I found threads dating back to 2015 about the created by field not getting mapped, and a couple from this past month as well. I suppose the original poster of this thread had a similar issue to mine and might not have explained it in as much detail or provided enough screenshots to be clearly understood as the same issue I am facing.
In the end, I will never hold my breath for Bubble to add new features, but I’ll continue to raise my voice to express my ideas of how certain new features could be very beneficial not just for me, but the community at large.
One of the major use cases for the need to have the created by field mapped to a login to existing account is a shopping cart in which users can select products without being logged in. What brought me here is my work for a client who wants to iterate over the point in the sales process that a user is forced into logging in or creating an account. I’m sure there are a lot of other users who are building e-commerce platforms that would benefit from the same mapping of created by that is done for a newly created account to be done for a login to existing account.
Hopefully the API issue would be fixed, or at least Bubble support would point out what I’m doing wrong there.