Have a few use cases for this question.
We have a schema/object type of Employee with Manager as an attribute of the Employee which is a self object reference back to the object type of Employee.
If you are the Manager you would have inbound references of other Employees, including those that have a status of Terminated.
Is it possible to alter the view from the Manager Employee object so they only see the Active employees from their Asset page. Without removing the Manager's name from the Manager attribute in their former reportee's Employee object. We use that information if there are outstanding assets/actions/tickets left connected to the former employee.
TIA
I suppose you mean within the assets scheme itself on the object?
Then the answer is no, you can't filter a reference. a reference is created and then all the options in the reference are available.
These can't be filtered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi I was wrong in the begining.
You can filter a referenced attribute, on the attribute select the 3 dots to access the attribute settings.
You there have an option to filter by AQL, to referenced objects.
So in you case you could add an AQL, to filter out the Employees that are terminated as options for the reference.
So if you use the attribute status for this, you could as example use AQL: "Status" IN ("Active")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't believe that would work. The object is the employee and the attribute is Manager. So if a Manager was to look at their own employee object they would have inbound references for employees that report to them. Filtering on the attribute as you suggest, would only limit the ability to select an "active" employee as a manager. The manager would still see inbound references to them from terminated employees no?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct, but this is based on your setup.
Otherwise with other references this will work.
So in your case there is no solution as your relations, in a way are a loop from employee to manger and from manager back to employee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another use case is that we have team attributes, which exists on the employee record. When you look at the team and see the inbound refs - it shows all employees ( active and terminated) as part of the Team object.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.