You only need to use a "Search and Link" QuickAction (the first action in your composite action).
InsertChildObject always does an Insert. Is there a special reason you want to use it?
I am now using only the search and link in the quick action and still no luck matching the Customer (ProfileLink) on the Incident to the Owner on the CI.Workstation. Could it be the relationship I'm using? See attached.
WORKSTATION.docx 75.6 K
The field "Owner" always stores the LoginId but $(ProfileLink) always uses the customer's Recid.
You can't access the Owner_Valid field afaik (this contains the RecId) but you can use the customer's LoginId instead. This field is populated every time you change the ProfileLink:
You don't neccessarily have to create a new relationship for this. You can use the standard relationship as well and only select the sub type:
I don't know your use case but another option is to create a new tab which is showing all the CIs associated to this user with a link filter.
When you click on "link" in this tab only the CIsassociated with this user will show up:
$([OtherObject]CIType != "Service" &&
[OtherObject]Status not in ("Disposed", "Archived"))
Thank you, The first scenario is what I am looking for, but I would like only the Workstation CI to populate, If I use only the second "dummy link" I get not return. If I combine the 2 I get all the CI's related to the customer.