i have two tables TPS Interchange and TFM Trinary. Primary key of TFM Trinary is foreing key of TPS Interchange which is Trinary_id . TFM Trinary contains key Column which has some text data like TESTCALL, TESTEMAILalso created a record type TPS Interchange and record type TFM Trinary . Now i want to create an custom field like if 'recordType!TPS interchnage.Trinary_id = 15 then it showsTFM Trinary .key= TESTCALL if 'recordType!TPS interchnage.Trinary_id = 20 then it showsTFM Trinary .key= TESTEMAIL otherwise Default nullHow to do this ?
Discussion posts and replies are publicly visible
when creating a custom field make sure to select write your own expression and Real-time evaluation as it will allow you to use related record field.then by the use of a!customFieldMatch() we can achieve this, for example ->
a!customFieldMatch( /*my 'recordType!TPS interchnage.Trinary_id*/ value: 'recordType!{42fe68dc-1205-4240-bb84-1cb3065c6210}AT temp2.fields.{7e0ab763-a70a-43c1-95c9-8304cc937922}tempId', equals: 15, then: "TESTICAL", equals: 20, then: "TESTEMAIL", default: "null" )
hi Klaus34 go to your record and follow the below step:
click on new custom record filed:
select write your own expression: it allows related record fields also
write your expression here: example :
a!customFieldMatch( value: recordType!Order.relationships.customers.fields.supportLevel, equals: 3, then: "Critical Customer Order", default: "Customer Order" )
select & give your custom record filed name and select data type of your field
after completing it will be created and visible in your record as below:
AFAIK sync-time evaluation doesn't allow related record field and a!customFieldMatch() as it says in the screenshot ->
a!customFieldMatch () will work only for Real-Time Custom Record Fields
Hello Klaus34 ,
Refer documentation to know more about custom record fields. https://docs.appian.com/suite/help/23.4/custom-record-fields.html
Klaus34 Any of the above would work here considering that the 'Trinary_id' is present in the base record where we are creating the custom record field so we do not need related record fields. So we can use any of them. The real-time will need more evaluation time as it will evaluate the values in the real-time. And sync time is calculated when the data is synced.
For a more performant view, I will advise using sync time evaluation along with if() function to check.
The data is present in the base record. This isn't coming from a relationship. Hence your a!customFieldMatch's value parameter is incorrectly configured if you have added it for this specific usecase.
Abhishek Karumuru said:value: recordType!Order.relationships.customers.fields.supportLevel,
Hi Klaus34,
try with this it will help instead of calling a!customrecordfields() it has the feature compatibility issues.
I think he has highlighted in the image saying to opt real-time evaluation. and the customFieldMatch is an example I assume.
yes as I mentioned