Conditional transform working in sandbox but not production?

[pholdridge (Peter Holdridge)]

This works in my sandbox environment, but not in production.

There was an exception while calculating the value for this attribute. Error rendering template: $EmpStatus eq Leaveofabsence

"isLOA": {
    "type": "conditional",
    "attributes": {
        "EmpStatus": {
            "type": "replace",
            "attributes": {
                "input": {
                    "type": "identityAttribute",
                    "attributes": {
                        "name": "employmentStatus"
                    }
                },
                "regex": "\\s",
                "replacement": ""
            }
        },
        "expression": "$EmpStatus eq Leaveofabsence",
        "positiveCondition": "true",
        "negativeCondition": "false"
    }
},

[sharvari (Sharvari Shah)]

It’s probably because the $EmpStatus may be null. Trying the transform as below:

"isLOA": {
    "type": "conditional",
    "attributes": {
        "EmpStatus": {
            "type": "replace",
            "attributes": {
                "input": {
                    "type": "firstValid",
                    "attributes": {
                        "values": [
                        {
                            "type": "identityAttribute",
                            "attributes": {
                                "name": "employmentStatus"
                            }
                        },
                        {
                            "type": "static",
                            "attributes": {
                                "name": "NONE"
                            }
                        }
                        ]
                    }
                },
                "regex": "\\s",
                "replacement": ""
            }
        },
        "expression": "$EmpStatus eq Leaveofabsence",
        "positiveCondition": "true",
        "negativeCondition": "false"
    }
}

[pholdridge (Peter Holdridge)]

$EmpStatus is pulling the “employementStatus” identity attribute which has a value of “Leave of absence” in it. It then strips the spaces from it for the expression to compare.

Even if the identity attribute value were missing, the ‘NONE’ value would be returned and the expression would result in “false” and not error.

Please pay attention to what I posted. I already said that the data and the code match from sandbox. It works there, but not in production. This is a bug in production in my opinion.

I believe there is an “order of operations” issue in production and it’s not calculating the $EmpStatus value correctly.

[tyler_mairose]

Hello @pholdridge,

I get the same message “Error rendering template: $EmpStatus eq Leaveofabsence” with your transform when the identityAttribute I use is not mapped.

For example, using the identityAttribute firstname would work but personalEmail would give the “Error rendering template” message.

Can you verify that employmentStatus is mapped correctly in production?

Also as a note, it is not recommended to use identityAttributes during the calculation of another identityAttribute. We recommend using the accountAttribute transform when calculating other identity profile attributes.

This excerpt is pulled from the identityAttribute docs on our site.

• This transform is not intended for use within an another identity profile attribute’s calculation. Identity attribute calculations are multi-threaded processes, and there is no guarantee that a specific attribute has current data, or even exists, at the time of calculation within any given transform. Referencing identity attributes within another identity attribute’s calculation can lead to identity exceptions.

[pholdridge (Peter Holdridge)]

I can confirm that employementStatus is populated with data. I see it on all identities and in preview.

We wanted to use Identity Attributes because it would require us to “hard code” a source name in the transform, which we prefer to avoid when possible.

Again, I want to emphasize for the third time that Sandbox works with the same data and same transform code. Please confirm if this works with your testing in Production before your next reply?

If we have no other choice, we will use an account attribute.

[tyler_mairose]

Thank you for confirming that.

I can confirm I am testing using a production environment.

I do see that the attribute is called employementStatus with an e after employ and in your transform code you are pulling the identityAttribute employmentStatus without the e.

Is the transform you posted the one you are using or is that just a mixup in copying here to the forum?

[tyler_mairose]

Hello @pholdridge,

I wanted to check-in with you. Did my last reply solve your issue? If not, I’d love to help debug and see what’s going on

[KevinHarrington]

Instead of specifying the input you can just use the OOB field mapping interface available in the front-end. Then as your first value (in place if your “identityAttribute” transform) in your “firstValid” you could use:

{
"attributes": null,
"type": "trim"
}

This should get around specifying either an Identity Attribute or hardcoding a source name in our transform.

[pholdridge (Peter Holdridge)]

I appreciate it but I don’t know what you mean by this since I’m still fairly new to IDN. I’ve had to learn quickly in the last 2 months. Perhaps you can provide an full code with your proposal and explain it again?

[KevinHarrington]

The problem as I understand it is that the first value in your nested “firstValid” transform references an Identity Attribute. And the alternative that you stated was to use an “accountAttribute” transform. But there is another option - to reference the value as it is configured in the front-end in the “Identity Profile” configuration screen. The easiest way that I have seen is to call a “trim” transform as a placeholder.

"isLOA": {
    "type": "conditional",
    "attributes": {
        "EmpStatus": {
            "type": "replace",
            "attributes": {
                "input": {
                    "type": "firstValid",
                    "attributes": {
                        "values": [
                        {
                            "type": "trim",
                            "attributes": null
                        },
                        {
                            "type": "static",
                            "attributes": {
                                "name": "NONE"
                            }
                        }
                        ]
                    }
                },
                "regex": "\\s",
                "replacement": ""
            }
        },
        "expression": "$EmpStatus eq Leaveofabsence",
        "positiveCondition": "true",
        "negativeCondition": "false"
    }
}

[pholdridge (Peter Holdridge)]

When you say “front end” do you mean the mapping tab in IDN Identity Profile?

Source: XXX / Attribute: Employment Status / Transform:

Thanks for the help by the way…

[pholdridge (Peter Holdridge)]

This seems to work. Thank you so much man!

[derek_putnam]

Huzzah! I’m so glad we were able to get you an answer, Peter! Don’t forget to checkout all of our docs on transforms, and please come back if you have any questions.

If you ever have feedback, for example something that’s missing from our docs, like us know over in the #community:feedback category!