Azure B2C Sign In & Sign Up custom field still showing asterix on non-mandatory field

Neil Hodges 0

Were using Azure B2C and specifically the Sign In 7 Sign Up User flow with our own Sign up template.

I have added a custom field - 'Mobile Number' and we had previsouly set it to be mandatory. This rightly shows an asterix next to the label to inform the user this field is mandatory.

We now do not wish for the filed to be mandatory, so we have seleccted that this filed is option, thus not setting it as mandatory.

The Asterix persists on the form label, which is confusing users, i have tried to invalidate the cache, but still it persists?

How can i force this asterix to stop showing up on the label?

When submitting the form, the validation does not trigger for the form field, so i can only think this is a bug in azure B2C and the cache?

Shweta Mathur 28,031 Reputation points Microsoft Employee

2024-05-02T06:43:39.4966667+00:00

Hi @Neil Hodges ,

Thanks for reaching out.

Could you please confirm what steps you followed to setup the custom field as mandatory in the user flow?
Neil Hodges 0 Reputation points

2024-05-02T09:48:46.9266667+00:00
Hi Shweta

The steps are as follows:

Login into B2C tenant.

Access 'User Flows'

Select - 'B2C_SignIn_SignUp'

Select 'User Attributes'

Add Attribute - 'Mobile Number' as DataType = String

Go back to 'B2C_SignIn_SignUp'

Select Page Layouts, and select 'Local account sign up page'

Then in the list of User Attributes, set 'Mobile Number' to be Optional = Yes

Please see screenshot.
Shweta Mathur 28,031 Reputation points Microsoft Employee

2024-05-03T05:16:19.31+00:00

@Neil Hodges I also tried the same steps and (*) is not persist in my case.

Setting as mandatory

Optional

Are you facing issue with all versions of page layouts?
Neil Hodges 0 Reputation points

2024-05-03T13:25:59.1633333+00:00

Hi,

This is the only layout we're having issues with. It's the only one we've originally set a field to Optional = No, and now back to Optional = Yes.

It's like it's caching the label, and not removing the asterix (*).
But ive done everything I can think of for invalidating the cache, I thought time would sort it out, but it's persisted for weeks now. I think this is a bug with custom templates?

Share via

Azure B2C Sign In & Sign Up custom field still showing asterix on non-mandatory field