Hi, the unique field has been in the platform for quite some time. For your question related to coalescing in a transform map...you would want to use that regardless of the unique key if you are trying to either update the found record or create new if it doesn't exist. If you didn't check the coalesce box, then another record will attempt to be created, if it can't, because of a unique key setting, then it'll probably add an error to your log and the resulting record won't be created. So coalescing is still recommended as a leading practice to prevent all that and organize your transform appropriately.
Yes. Much like coalesce on a transform map, all values must be unique to do an insert. If you use Unique on two fields, the combination of both fields must be unique as well as the individual values. Use it carefully. Ex: Record has field1 and field2 with values foo and bar respectively, no other records can have field1 foo, and no other fields can have field2 bar.
Interesting - when I follow this instruction on the configure>table (Washington DC release), a "Unique" field is still created in the dictionary entry form. This is interesting as it creates a unique field anyways!🙃
Good job SN, finally ServiceNow added the unique key. Btw, should we use coalesce in transform map even if field is unique key?
Hi, the unique field has been in the platform for quite some time. For your question related to coalescing in a transform map...you would want to use that regardless of the unique key if you are trying to either update the found record or create new if it doesn't exist. If you didn't check the coalesce box, then another record will attempt to be created, if it can't, because of a unique key setting, then it'll probably add an error to your log and the resulting record won't be created. So coalescing is still recommended as a leading practice to prevent all that and organize your transform appropriately.
Is this applicable for two fields as unique in a table ?
Yes. Much like coalesce on a transform map, all values must be unique to do an insert. If you use Unique on two fields, the combination of both fields must be unique as well as the individual values. Use it carefully. Ex: Record has field1 and field2 with values foo and bar respectively, no other records can have field1 foo, and no other fields can have field2 bar.
@@ChuckTomasi Thanks! I will try it out.
Really cool jewel of a tool! One more deduplication and data quality booster.
Interesting - when I follow this instruction on the configure>table (Washington DC release), a "Unique" field is still created in the dictionary entry form. This is interesting as it creates a unique field anyways!🙃
Great tip, thanks
Great tip, I’d turn these into shorts and share across google and TikTok
Super