Context:
Scorecast element: Users input their own text (question), then check Yes if completed or true.
Here is the workflow I’m currently trying. It’s showing as valid, but when I test it out, once the ‘Yes’ is checked and I refresh the page, it doesn’t save that ‘Yes’ to that question.
Data setup: Prospect (account)
Check box A
Check box B
Check box C
etc…
I understand it’s a convoluted way to organise my dataset, but it’s the easiest way for me.
Any help with the workflow would be muchly appreciated!
@J805 Thank you so much for going through the effort with this. Really appreciate it. I believe I’m a step closer, but still struggling with a few things. The ‘questions’ are user-input and not set Text Fields , does this change anything?
Secondly, the table I used was a generic table, is it better to have it as a repeating group like yours?
My second problem is that this checkbox unfortunately, stays the same across each different account. For example, it’s the same checkbox questions and yes/no results for ‘Gro Data’, as it is for another account
The questions can be set by the user. That’s no problem. You can use a table if you want but, to me, it’s just another one of Bubbles ‘half built’ idea that they never fixed all the bugs from. So I always use repeating groups. Up to you though.
Do you have privacy rules set up? What does your workflow look like? Let me know.
Yeah. I see what you are doing now. I recommend not using a separate field for each entry. Try the way I have it set up but just add privacy rules to make sure only the people that should see it does see it.
You only need one text field for the question and one field for the checkbox on the dataType.
Sorry @J805, it seems to work in your repeating group, but when I replicate that (even the data types) in my own table, it just doesn’t save the checkbox whatsoever
I also have quite a few workflows on the original ‘Champion Test’ that shows additional user-based inputs based on the previous question being empty or not.
I think with the Repeating Group, i’d need to change all of this.
It seems so easy as all I need is ‘When checkbox A is checked - make changes to checkbox A as YES’
Yeah. That doesn’t seem like the best way to set something up. As you can see in my example app, it really can be that simple. Just add privacy rules on top of it. A lot of workflows that ‘show’ something usually isn’t the most optimized way of doing things.
It’s something a lot of people struggle with when starting out in Bubble. Its really about understanding how to work with lists I think.
I need to restrict the visibility for each Account I.e. Prospect. The app is a CRM. I’m fine with the data privacy on a user-basis, but it’s not letting me limit it to each different account?
