why assessor or requestor fields are not present in smart assessment record

Amarnadh · 3 weeks ago

We wanted to show assessor and requestor in the list view of smart assessments but I can't find those fields in the record. How to achieve it?

Vikram Reddy · a week ago

Hi @Amarnadh,

Short answer: this is by design, not a field someone forgot to expose. The Smart Assessment Engine stores each assessment as an sn_smart_asmt_instance record, and that table is deliberately source agnostic. It doesn't carry a plain "assessor" or "requestor" field because SAE gets triggered from all kinds of source tables (controls, risks, cases, DRIR, whatever), and the engine doesn't want to hardcode identity fields for every possible trigger.

What you're actually seeing as "assessor" in the workspace is the Contributors relationship, not a plain reference field on the instance. When an assessment is created, the owner adds contributors (that's your assessor), and that's stored as a related list, not a column, which is exactly why it won't dot-walk into a classic List View column the way a normal reference field would. Requestor is similar: whoever kicked off the assessment (usually via the Trigger Smart Assessment flow action) stays tied to the triggering record, not duplicated onto the instance.

A couple of things worth checking before you build anything custom. First, if you're working out of the Compliance/Audit Workspace or the GRC Tasks page, ask your admin whether column personalization is enabled there, since that page can expose columns like Entity or Attestation Respondent through the cog icon without any dev work. Second, if you are dot-walking a legitimate reference field and it's still showing blank in a regular list view, don't assume the data's missing, check the ACL on the underlying field first. There's a known Now Support issue (KB2662189) about dot-walked fields on the assessment instance question table not rendering in List View purely because of read ACL restrictions, even though the same field is visible on the form.

If after that assessor and requestor genuinely aren't retrievable as data (not just hidden), the practical fix is a small business rule or a step in your Trigger Smart Assessment flow that copies the contributor and the requesting user onto two plain fields you add to sn_smart_asmt_instance. Once they're real fields on the table, they behave like any other list view column and you can filter, group, and report on them normally.

References

Thank you,
Vikram Karety
Octigo Solutions INC
My Blog: glideandgen.com