using Account Attributes in your transforms is definitely the best practice unless there’s a solid reason to use an Identity Attribute, so I’m with @nandambk here.
also, for what it’s worth, you don’t need to specify all those 0
cases in the table, since that’s the default. you can simplify your transform to this:
{
"name": "expense approval limit",
"type": "lookup",
"attributes": {
"input": {
"type": "firstValid",
"attributes": {
"values": [
{
"attributes": {
"sourceName": "sourceName",
"attributeName": "level"
},
"type": "accountAttribute"
},
"noLevelSet"
]
}
},
"table": {
"10": "20000",
"11": "50000",
"12": "100000",
"13": "200000",
"14": "200000",
"15": "2500000",
"default": "0"
},
"requiresPeriodicRefresh": "true"
},
"internal": false
}