This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 75%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
Input validation in display controls stops working as expected when upgrading B2C custom policies based on "urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.6" to a page layout version higher than "2.1.6".
The result is that no error message is displayed to the user, as well as the "continue" button becoming active before the input validation criteria has been met.
Expected:
Actual (after update to 2.1.7/8)
Just for clarity - to make sure we compare apples with apples, below is the same custom policy but in page layout version 2.1.8
@Schalk Van Wyk • Can you clarify which API you are setting urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.6 for? The version for urn:com:microsoft:aad:b2c:elements:contract:selfasserted can be specified under api.localaccountsignin, api.socialccountsignup,api.localaccountsignup, api.selfasserted and other content definition IDs. I tried setting 2.1.6/2.1.7 for api.selfasserted but nothing break in my case.
Thanks for the reply.
Some background:
I have a technical profile using the "SelfAssertedAttributeProvider" protocol, this TP contains a custom display control (seen in the screenshots), which in turn has a number of ValidationClaimsExchangeTechnicalProfiles during the "SendCode" action, the first ValidationClaimsExchangeTechnicalProfile is a "ClaimsTransformationProtocolProvider" TP which has a "ConvertStringToPhoneNumberClaim" claims transformation - which is where the validation message should come from.
Below is the ContentDefinition being referenced in the TP:
<ContentDefinition Id="SelfAssertedContentDefinition">
<LoadUri>~/tenant/templates/AzureBlue/selfAsserted.cshtml</LoadUri>
<RecoveryUri>~/common/default_page_error.html</RecoveryUri>
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.6</DataUri>
</ContentDefinition>
Hope that helps. I've tried various combinations of this, but still no luck. The custom display controls seems to display strange behaviors at times.
The only thing I can think of is that some control is overwriting the error message, but why is that not happening in previous versions...