Skip to main content
Solved

What does one need to do to have Checkbox (BIT) values go lower case for use in Web connector body?

  • June 8, 2026
  • 3 replies
  • 15 views
M
Superhero

Struggling a lot to get a Web connector call to work, even though it gave a 201 response status code.

We have a Checkbox with a BIT data type in use and have this value used in the body of a call. In this example to set the two factor authentication type to “Password and TOTP token” and if one want to enable/disable “Allow fallback to em-mail”.

It turns out that the boolean value is starting with a capital letter (True):

{ "two_factor_authentication_type": 3, "allow_fallback_to_email": True }

After a test with setting the body value manually and not through a flow parameter it does actually change the requested data when it is lower case (true):

{ "two_factor_authentication_type": 3, "allow_fallback_to_email": true }

What do I need to do to have the parameter not be starting with a capital letter?

Best answer by Peter Verwijs

Hi Mark,

Can you try using a process procedure to convert the value of the boolean to a string with the lowercase “t” and then assign that to a different variable that is used as the input? Something like this:

if @enable_fallback_email = 1
begin
  set @enable_fallback_email_string = 'true'
end
else
begin
  set @enable_fallback_email_string = 'false'
end

Please let me know if this fixes the issue for you.

Kind regards,
Peter Verwijs

    3 replies

    Peter Verwijs
    Moderator
    Forum|alt.badge.img+2

    Hi Mark,

    Can you try using a process procedure to convert the value of the boolean to a string with the lowercase “t” and then assign that to a different variable that is used as the input? Something like this:

    if @enable_fallback_email = 1
    begin
      set @enable_fallback_email_string = 'true'
    end
    else
    begin
      set @enable_fallback_email_string = 'false'
    end

    Please let me know if this fixes the issue for you.

    Kind regards,
    Peter Verwijs

    M
    Superhero

    ​@Peter Verwijs  Making it a string value does work. I guess that means a BIT data type is not considered a usable data type for a Boolean in the Web connector.

    Would you think it would be worth for me to create an idea to implement some kind of convert data type option for the web connector to support BIT → Boolean? Or was my choice for using BIT wrong from the start?

    M
    Superhero

    Created an idea to convert a BIT value to a true Boolean for use in the Web connector here:
     

     

    Terms & ConditionsAccessibility statement