Hi Laurence,
Will these two technicians ever switch positions (i.e. will one of them be Primary SA on one order and the other is Secondary but then they play the other role for other service orders?).  Right now we don’t have a way to specify whether the picture was uploaded by a primary or secondary tech but you could probably do something with the Classification Level 1 or Classification Level 2 fields and just instruct them to enter different values in there depending upon their role on the current service order.  Or we could do a small customization where the Comments field gets prepopulated with a prefix string of “Primary tech: “ or “Secondary tech: “ based on which tech was assigned at the order header level or something along those lines.
Thanks,
Reid

Hi Reid,

Thank you. They don’t switch role, and 1st tech attachments are on the checklist, while the second tech attachments are on the Service Order level.

We don’t want them to type any additionnal data. We thought about identifying attachments with the attachment_id type field and the surrogate…. fields in the table. Can you please confirm this will be secure ?

Thanks

Hi Laurence,
If you’re going to do something at the Alliance code or DB level to indicate this you should be able to get this information directly from the ap_attachments table.  There’s a field in there called ap_user_login which stores the user ID of the person who created the attachment record so you could probably compare that to the service_call.sa_person_id field on the service order (if those values match then the attachment was uploaded by the primary SA and if they do not match then the attachment was uploaded by a secondary SA).  I’m not an expert in the Alliance customizer app but maybe you could add a computed column in there which displays between the Attached By and Comments fields that indicates “Primary SA” or “Secondary SA” depending on whether these values match or not (that should be easier than trying to determine the link by using the ap_attachment_id and surrogate_ap_attachment_id values):

Thanks,
Reid