ERROR - Urgent - Can't define Array variable
# 🤝help
s
Each time I try to define a variable (workflow, user), it gets reverted to string, even though other options stay as set for Array. I can't store data table results because the variable is recognized as a string, not an array. There is no way to save array. https://cdn.discordapp.com/attachments/1250567994535444490/1250567994724323368/image.png?ex=666b69b4&is=666a1834&hm=34e735e7fec03d6c35ff653029e3564357e4007273ae6b92f932e19356e8ab17&
l
Instead of string use array or object from the drop-down of type
s
I think I didn't explain—I can't use anything. The type defaults to String, and none of the types can be selected. What is more, I hope Botpress didn't default all existing variables to String. This would mean that all bots have errors, and it would be a nightmare to fix them. @limited-pencil-78283 you can't have Array Type at the bottom if you select the main Type as a string - this screenshot shows the error in botpress. I believe that nobody can select anything but String type. Try to save it and open again to check what type it has.
s
Yes, and I think it's a bigger bug because you can also check information from @boundless-pharmacist-77949 - he changed the card, and it's not recognized. The software still uses the previous one.
I hope Botpress didn't default all variables to strings. This would mean that all bots for everybody don't work anymore as expected unless they use only string variables. I checked one old variable and instead of being boolean, it's string right now. I hope it's only the UI issue so I will not check anything till they fix it - I hope soon.
@plain-lifeguard-16679, @freezing-elephant-85019, @bumpy-butcher-41910 Do you know why the variables default to String and it's not possible to change the type of variable? It doesn't matter if the scope is Workflow, User or Bot. Since yesterday I can't do anything and don't know if this will be fixed today because I need to finish one implementation?
b
I'm fairly certain this is a visual bug in the variables panel
thanks for flagging this though, obviously it should be showing correctly. it's just the list that's defaulting to the first option when it's being displayed
but as you can see in the capture card, the variable is the right type
112 Views