Ideas
0
Under review
Person update with WAMI instead of EmployeeNumber
Carol Wapshere 4 years ago
in UNIFYBroker/Aurion
•
updated by Matthew Davis (Technical Product Manager) 2 years ago •
3
Topic collaborators
Hello Unify people. A long time ago I posted this:
https://voice.unifysolutions.net/communities/6/topics/2467-aurion-export-failed-employee_no-expected
I have now found out it is not (or no longer) a requirement of the Aurion API method EMP_UPDATE_PERS to have the employee number, and it can work with the WAMIKey, as in the following:
API_FUNCTION=EMP_UPDATE_PERS|WAMI_NO=16798|CONTACT_PHONE=02 9898 9898|WORK_MOBILE=0404 040 404
If the customer asks for an update to the Aurion connector to use the WAMI if Employee_Number is not available, can you do that?
Customer support service by UserEcho
Hey Carol,
If the EMP_UPDATE_PERS function can have the WAMI_NO field populated instead of the EMPLOYEE_NO field, then we can certainly look at adding that as an option on the person connector.
Thanks Matt! I will ask the customer to send through a request.
Carol - the customer was advised today that work has now commenced on this feature request with a view to an advance release for them prior to it being available to all customers in the usual way.