I want a user to be able to create data that can be viewed by anyone to whom he/she gives the access_code. Therefore, on signup workflow (using standard Bubble Signup form), I create an access_code for the new user (using the Calculate RandomString function) and store it in the access_code field of the User table. (I added the access_code field to the User table.)
I have a separate table for the (semi-public) data. Therefore, in a second action for the SignUp event, I (try to) store in the access_code field of the data table the newly created access_code (which should now be the “current user’s access_code” created in the preceding action). I do this by storing the “current user’s access_code” in the access_code field of the data table.
BUT, Bubble stores two different access codes in the two tables (viz., the User table and the data table). I only call the “Calculate RandomString” function one time (in the first of the two work flow actions), so I cannot understand how two different codes are being generated. I modify the User table with “access_code = Calculate RandomString” in the first action, and I (try to) modify the data table with “access_code = Current User’s access_code” in the second action. That does not work and I get two different codes in the two tables.
The only way I was able to prevent this was to wait until I navigated off of the page before executing the second action. Then on the page load event of the next page, I stored the current user’s access_code in the data_table. That works.
This is just plain weird and I suspect that it is a bug.