Azure-docs: Can not Customize the type of a User Attribute

Created on 4 Jul 2019  Â·  7Comments  Â·  Source: MicrosoftDocs/azure-docs

I can not change the type of the User Attribute from a TextBox Input to a CheckBox

I have created a set of new User Attributes and used them in my new User flow (Policy) in Azure AD B2C.

These attributes are of data type "Boolean" but when I run the user flow I get a textbox input instead of a checkbox.

Usually, I get the possibility to change it on the portal but now I can not find where to do so now.

Have anything changed?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

B2subsvc active-directorsvc awaiting-product-team-response cxp product-issue triaged

Most helpful comment

Go and select the User Flow that you created in the Azure Portal.

  1. Select Page layouts.
  2. Select Local account sign up page.
  3. Under User Attributes, find your attribute which should be a Boolean.
  4. Set User input type to CheckboxMultiSelect.

Then go to the Languages menu within the User Flow.

  1. Enable Language Customisation.
  2. Download the English default language file for the Local account sign up page.
  3. Look for the extension attribute name within "LocalizedCollections".
  4. Add a value as follows:
    https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-language-customization#provide-a-list-of-values-by-using-localizedcollections

"Items":[ { "Name":"Agree", "Value":"True" }

Save your file and upload it as an override to the English localisation.
You should now see the checkbox and it will return True when selected, and False when not selected.

All 7 comments

Hi @thesilvereagle - Thank you for your feedback! We will review and update as appropriate.

Hi @thesilvereagle ,

I tested in my tenant today and had the same problem. My boolean custom policy (Allowed) is also showing as a textbox.
image

It would only accept the words "True" and "False" as values. This seems like a product bug to me and even if there is a way around it, it is not well-documented. I am escalating this to the product team to request a fix.

In addition, the email verification code took a very long time to reply so that might also be worth looking into on the PG side.

CC: @mmacy

Go and select the User Flow that you created in the Azure Portal.

  1. Select Page layouts.
  2. Select Local account sign up page.
  3. Under User Attributes, find your attribute which should be a Boolean.
  4. Set User input type to CheckboxMultiSelect.

Then go to the Languages menu within the User Flow.

  1. Enable Language Customisation.
  2. Download the English default language file for the Local account sign up page.
  3. Look for the extension attribute name within "LocalizedCollections".
  4. Add a value as follows:
    https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-language-customization#provide-a-list-of-values-by-using-localizedcollections

"Items":[ { "Name":"Agree", "Value":"True" }

Save your file and upload it as an override to the English localisation.
You should now see the checkbox and it will return True when selected, and False when not selected.

Thanks @JasSuri . It seems like it is working perfectly. Though, there is still another issue as I can not get to the User input type editor on some of my User Flows (I think that this issue is present only on the User Attributes that their Input Type were set already, which means they can not be modified once set)

I think the problem is that if you already enabled language customisation, then you add the Boolean attribute, the UI no longer prompts to add the "values" when you select user input type checkbox. But if you have not yet enabled language customisation, then when you choose user input type checkbox, it will prompt to provide values then and there.

There is an assumption being made that in the background you are doing language customisation to achieve this, therefore if you already enabled language customisation then there is an expectation to configure it there without any hint. @mmacy

This is confusing, so we shall at least get some backing documentation.

You should be able to change user input type at all times, I am not aware when you cannot.

Yes, right. I disabled language customization and it seems like it is working perfectly. Thanks for backing me with such a great explanation :D

@JasSuri is there a work item for this or ETA? Can we get an update to this thread when the documentation is added?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Ponant picture Ponant  Â·  3Comments

DeepPuddles picture DeepPuddles  Â·  3Comments

spottedmahn picture spottedmahn  Â·  3Comments

bityob picture bityob  Â·  3Comments

ianpowell2017 picture ianpowell2017  Â·  3Comments