Hey All,
I am not certain this is a bug just yet, but I have never seen this behavior before and I have been building on Bubble for nearly 6 years, anything from simple one-page forms to complex ERP systems.
Recently, I have been building out a transaction (real estate) management system for a family member and one of the functions is a CRM. I have a “Contact Details” view that allows for updating of needed contact information. These contacts are using the default ‘User” type with some extra fields.
My Save button is wired up to two custom event triggers that are conditional, based on the type of User. Either it is an “individual” or a “company”. This is where my problem lies. Sometimes the button works, sometimes it doesn’t, and when it doesn’t, the Bubble logs don’t even record the button was clicked in the first place.
My first thought was that the “Parent Group User” was not always getting loaded meaning it didn’t meet one of the two conditions, but that can’t be true since the contents of the page are populated from the same source. I am doing a “Do a Search For” on the URL value after details to match to a specific user.
Just to be safe, I added a step before the conditionals to throw up a Toast alert to say the button has been clicked. To my surprise, for the Users that don’t play nice, the Toast never triggers either. It also doesnt hit the breakpoint flag on the button click action in debug mode on “Step-by-step”. This has me stumped because, regardless of what is going on in the following steps, the Toast should always trigger. I have zero restrictions or conditionals on the button itself. Even weirder still, when I remove the custom event triggers all together, it works 100% of the time.
What is my Event doing you might ask? Nothing overly complicated. There are a few steps, but most are fairly simply functions that are just updating fields assigned to the contactRecord.
I spent about 3 hours on Sunday completely rebuilding, from scratch, all of the flows and logic to see if it was something I was doing and, best I can tell, it doesn’t like something in the update process but I cannot, for the life of me, figure out what. What makes this especially more perplexing is all of the original logic used to work just fine until a week or two ago (hard to pinpoint when it stopped since the sole user of this application does not use it frequently, yet, since we are still building).
If anyone has any ideas on what would prevent this from working, and more importantly, note even throwing an error in the logs, I am at my wits end and would greatly appreciate any suggestions.
