Issue with passing locale to Claim Transformation

Question

Issue with passing locale to Claim Transformation

Soni, Ashish 21

Hi @Shweta Mathur @AmanpreetSingh-MSFT ,

Could you please help me with below issue?

We are using custom email service to send OTP for email verification. In order to achieve this, we are using ClaimTransformation to generate JSON request for the custom service.

In Extensions file, ClaimTransformation looks like this:

<ClaimsTransformations>
      <ClaimsTransformation Id="GenerateEmailRequestBody" TransformationMethod="GenerateJson">
        <InputClaims>
          <InputClaim ClaimTypeReferenceId="email" TransformationClaimType="email"/>
          <InputClaim ClaimTypeReferenceId="otp" TransformationClaimType="otp"/>
        </InputClaims>
        <InputParameters>
          <InputParameter Id="language" DataType="string" Value="{Culture:RFC5646}"/>
        </InputParameters>
        <OutputClaims>
          <OutputClaim ClaimTypeReferenceId="emailRequestBody" TransformationClaimType="outputClaim"/>
        </OutputClaims>
      </ClaimsTransformation>
    </ClaimsTransformations>

When we try sending the request, our service gets only "en" as request. Expectation is to recieve a json request with email, otp and locale value. Other fields are not present in request.

Could you please confirm what am I doing wrong here?

Thanks

Ashish

Soni, Ashish 21 Reputation points

2023-03-15T08:54:33.3766667+00:00
Thanks @Shweta Mathur

Unfortunately, I am still observing the same behavior.

We are expecting the output json to look like below:

{ "email": "someone@microsoft.com", "otp": "123456", "language": "en" }

I tried the provided solution as well. When calling an API with request as "emailRequestBody", API recieves only "en" in request body.

Thanks

Ashish

Shweta Mathur 12,906 Microsoft Employee

Could you share the claim type of emailRequestBody you are defining?

B2C can only build a JSON from its own claim type primitives. Which are int, boolean, datetime, string, stringCollection.

Did you try to pass below in output claims


<OutputClaim ClaimTypeReferenceId="email" />
<OutputClaim ClaimTypeReferenceId="otp" />
<OutputClaim ClaimTypeReferenceId="en" />

with these definiations:

 <ClaimType Id="email">
    <DisplayName>email</DisplayName>
    <DataType>string</DataType>
  </ClaimType>
  <ClaimType Id="otp">
    <DisplayName>otp</DisplayName>
    <DataType>string</DataType>
  </ClaimType>
  <ClaimType Id="language">
    <DisplayName>language</DisplayName>
    <DataType>string</DataType>
  </ClaimType>

and JSON output would be like

{
      "email": "someone@microsoft.com",
      "otp": "123456",
      "language": "en"
}

Soni, Ashish 21

@Shweta Mathur Here it is:

<ClaimType Id="emailRequestBody">
        <DisplayName>request body for Marketing Automation to send email</DisplayName>
        <DataType>string</DataType>
      </ClaimType>

Soni, Ashish 21 Reputation points

2023-03-15T14:28:25.31+00:00

@Shweta Mathur We need to pass user's locale in the emailRequestBody. Therefore, It can't be hardcoded.

When using Culture:RFC5646, the whole json is being replaced with a string "<user_locale>" . Ideally, it should replace only the value of language attribute.
Shweta Mathur 12,906 Reputation points Microsoft Employee

2023-03-16T07:05:27.09+00:00

@Soni, Ashish Did you tried using {Culture:LanguageName} in place of Culture:RFC5646 to get only ISO code for the language.
Soni, Ashish 21 Reputation points

2023-03-16T07:38:41.58+00:00

@Shweta Mathur Yes I did. It just replaces the whole JSON with the languageName.

Soni, Ashish 21 Reputation points

2023-03-15T08:54:33.3766667+00:00

Thanks @Shweta Mathur

Unfortunately, I am still observing the same behavior.

We are expecting the output json to look like below:

{ "email": "someone@microsoft.com", "otp": "123456", "language": "en" }

I tried the provided solution as well. When calling an API with request as "emailRequestBody", API recieves only "en" in request body.

Thanks

Ashish
Shweta Mathur 12,906 Reputation points Microsoft Employee

2023-03-15T10:57:49.2766667+00:00

Could you share the claim type of emailRequestBody you are defining?

B2C can only build a JSON from its own claim type primitives. Which are int, boolean, datetime, string, stringCollection.

Did you try to pass below in output claims

<OutputClaim ClaimTypeReferenceId="email" /> <OutputClaim ClaimTypeReferenceId="otp" /> <OutputClaim ClaimTypeReferenceId="en" />

with these definiations:

<ClaimType Id="email"> <DisplayName>email</DisplayName> <DataType>string</DataType> </ClaimType> <ClaimType Id="otp"> <DisplayName>otp</DisplayName> <DataType>string</DataType> </ClaimType> <ClaimType Id="language"> <DisplayName>language</DisplayName> <DataType>string</DataType> </ClaimType>

and JSON output would be like

{ "email": "someone@microsoft.com", "otp": "123456", "language": "en" }
Soni, Ashish 21 Reputation points

2023-03-15T11:00:42.9966667+00:00

@Shweta Mathur Here it is:

<ClaimType Id="emailRequestBody"> <DisplayName>request body for Marketing Automation to send email</DisplayName> <DataType>string</DataType> </ClaimType>
Soni, Ashish 21 Reputation points

2023-03-15T14:28:25.31+00:00

@Shweta Mathur We need to pass user's locale in the emailRequestBody. Therefore, It can't be hardcoded.

When using Culture:RFC5646, the whole json is being replaced with a string "<user_locale>" . Ideally, it should replace only the value of language attribute.
Shweta Mathur 12,906 Reputation points Microsoft Employee

2023-03-16T07:05:27.09+00:00

@Soni, Ashish Did you tried using {Culture:LanguageName} in place of Culture:RFC5646 to get only ISO code for the language.
Soni, Ashish 21 Reputation points

2023-03-16T07:38:41.58+00:00

@Shweta Mathur Yes I did. It just replaces the whole JSON with the languageName.

Answer 1

Hi @Soni, Ashish ,

Thanks for reaching out.

I understand you are trying to get claim values ('email', 'otp') or constants ('en') to generate a JSON string but only getting locale value in the JSON.

To get claim values and constants to generate a JSON string, you need to add JSON objects to JSON array following dot notation which is used to indicate where to insert the data into a JSON string.

<ClaimsTransformations>
      <ClaimsTransformation Id="GenerateEmailRequestBody" TransformationMethod="GenerateJson">
        <InputClaims>
          <InputClaim ClaimTypeReferenceId="email" TransformationClaimType="value.0.email"/>
          <InputClaim ClaimTypeReferenceId="otp" TransformationClaimType="value.0.otp"/>
        </InputClaims>
        <InputParameters>
          <InputParameter Id="value.1.language" DataType="string" Value="{Culture:RFC5646}"/>
        </InputParameters>
        <OutputClaims>
          <OutputClaim ClaimTypeReferenceId="emailRequestBody" TransformationClaimType="outputClaim"/>
        </OutputClaims>
      </ClaimsTransformation>
    </ClaimsTransformations>

{
  "value": [
    {
      "email": "someone@microsoft.com",
      "otp": "123456"
    },

   {
      "language": "en"
    },
]
}

Hope this will help.

Thanks,

Shweta

Please remember to "Accept Answer" if answer helped you.

Issue with passing locale to Claim Transformation

1 answer

Activity