Trying to change the text for the Sign Up link, by using the createaccount_link StringID, produces the following error while uploading the policy on the portal:
Validation failed: 1 validation error(s) found in policy "B2C_1A_BASE_V1" of tenant "tenantname.onmicrosoft.com".The localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringIdThe localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringId
Other IDs, like "createaccount_intro" or "button_signin" are working. Is this a typo on the documentation or a bug on the Azure AD B2C?
Thank you for your help.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@galrito
Thanks for your feedback! We will investigate and update as appropriate.
Can you provide the line of XML that you used to produce this error?
Come on, @Court72 after 5 months you could give me a bit more than 8 days of margin to respond.
Can you provide the line of XML that you used to produce this error?
@JasSuri
<LocalizedString ElementType="UxElement" StringId="createaccount_link">Sign up</LocalizedString>
Thanks, I’ll check this for you.
We have the same problem. Also I would like to change the whole text on the top of the page but local_intro_username is not working either with the latest data uri: urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.0 so I needed to downgrade to 2.0.0 to be able to change the intro text.
Any help is appreciated! Thanks!
Ok i narrowed it down to the page contract version.
This works:
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:1.2.0</DataUri>
<LocalizedString ElementType="UxElement" StringId="createaccount_intro">#Don't have an account?</LocalizedString>
But this does not:
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.0</DataUri>
<LocalizedString ElementType="UxElement" StringId="createaccount_intro">#Don't have an account?</LocalizedString>
{
"error": {
"code": "AADB2C",
"message": "Validation failed: 2 validation error(s) found in policy \"B2C_1A_AAD_TRUSTFRAMEWORKEXTENSIONS\" of tenant \"b2cprod.onmicrosoft.com\".The localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringIdThe localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringIdThe localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringIdThe localized string with ElementType: UxElement and StringId: createaccount_link has an invalid StringId",
"innerError": {
"correlationId": "070f932c-f425-466a-a2c6-7b4ede13e951",
"date": "2020-10-15T09:52:44",
"request-id": "89276389-12da-43a8-a342-a7962913832d",
"client-request-id": "89276389-12da-43a8-a342-a7962913832d"
}
}
}
I will have the team check out the stringIds on the new 2.1.0 page contract, whether they were missed or whether the stringId changed.
Then for local_intro_username, this doesn't throw any error on upload for contracts 1.2.0, 2.0.0 or 2.1.0, but is only effective in 1.2.0 and 2.0.0, and ineffective in 2.1.0.
@galrito - GitHub closed this when PR 133829 was merged.
Is this still an open issue? If so, we can reopen the PR for you.
Can you try "createaccount_one_link" instead? Sorry for the updates that we made in recent versions that is causing your convenience. We'll be more careful in making such changes to make sure the StringIds are well aligned with previous versions.
For local_intro_username, can you try to use local_intro_generic instead? By default, it has a string "Sign in with your {0}", where {0} will be replaced with the sign in method, either "Username" or "Email".
@stevenxzhou it works with createaccount_one_link. Perfect, thanks. It would save a lot of grief if the docs stated that fact, though :)
local_intro_username has been working for me, but I can try local_intro_generic if you need the feedback.
Thank you very much.