Error on Approval Owner ID Email

Hey ​@MichelleW,

Try using:

((Approval.OwnerID.EMail))

in the To field of the notification template.

OwnerID on the Approval record represents the employee currently assigned to approve the document, and the EMail selector should resolve to that employee’s email address.

I would use the Approval object exposed by the notification template rather than referencing EPApproval directly.

Also, I’d verify that the AP Bill has an approver populated on the Approvals tab and that the employee/user has a valid email address configured.

Hope this helps!

((Approval.OwnerID.EMail));

((Approval.OwnerID.EMail))((Approval.DocumentOwnerID.EMail));

Please try this.

​@MichelleW ,Hi can you please try below suggestion.

1. Clear the To box completely on the notification template (or the mailing setup on the notification/schedule) and retype it as plain text. Don't paste from another field or an earlier template.
2. Use the field syntax for the To/CC/BCC boxes, not the body syntax. ((EPApproval_ownerID!EMail)) is body/subject token syntax, so the To box rejects it. In those boxes, use the field picker (the lookup next to the box) or a formula-style reference such as =[Approval.OwnerID.EMail], using the exact path the picker generates.
3. Check the path segments. They are case-sensitive, and the last segment is the Contact email field (EMail, capital M). OwnerID on an approval record points to a Contact, so OwnerID.EMail is a valid navigation only if the notification's source entity actually exposes the approval record.

Likely root cause to check

If your notification's source is the Bill (Bills and Adjustments), then Approval isn't part of that entity, so the token can't resolve and stays red. In that case, one of these usually works:

• Base the notification on a source that includes the approval record (for example an approval-based entity or a generic inquiry that joins EPApproval to the Contact), or
• Use an approval-map-driven notification, where the approver's email is resolved for you, instead of scheduling a separate one.