Can there be 2 related item pickers on the same form that allow you to select 2 different customers? I am using one to set the Primary User and would like to use another one to set a contact person but when I do this, it populates both fields even though I have set the picker to store the value in two separate fields. Just curious how to accomplish this. Thanks.
We did this, and it works great so long as both customers that are selected are in the same group. If customers from different groups are chosen (i.e. we have Customer - Internal and Customer - External group objects) then the first RIP gets cleared out when the second RIP is populated, and vice-versa like whack-a-mole.
Shouldn't be happening; Can you post the configuration of the related item pickers as well as the link criteria on the relationships they point to?
FYI - we renamed the Incident BO to "Ticket"
Ah, I think I've found the issue - You can't place 'CustomerInfo' as an attribute on more than one customer.
That's probably why it's clearing out your other relationship.
CustomerInfo defines the current Requestor, for the client's purposes... Such as clicking the 'Customer' menu and viewing the current customer, or filtering the CI's on the currently selected customer.
Remove that attribute on one of the two items, and you should be okay.
Thanks for looking at this, Doug, but- unfortunately- removing the CustomerInfo attribute one one of the relationships had no effect. I say that it's clearing out the other RIP, and it is, but it is also inserting the word "record" in place of what ever was there, originally, in the RIP display field (although if you exit/ go home and come back to the Incident form, the RIP is, then, empty).
Are you making sure when you select the relationship you are selecting the correct relationship and when you select the display value its referring to the correct field.
We have this on an order form.
Relation - Specifics links Ordered For (relationship to customer table storing customer recid and name in speciifcs under Ordered For RecID and Ordered For Full name).
Relation - Specifics Links Approver (Relationship to customer table storing customer recid and name in specifics under Approver RecID and Approver Full Name).
Related Item picker 1 must select "Ordered For" relationship and the display field "Ordered For Full Name)
Related Item Picker 2 must select "Approver" relationship and the display field "Approver Full Name")
It looks like both of these relationships are using 'Customer Type ID' on Incident to track the relationship type.
Can you try a separate field? Or on your alternate customer relationship, set it to set that manually when added?
Your Public ID value on Customer is still the Full Name field, right?
We have them set to List of values in the related item picker. They work in our instance.
Yes the public ID is Full Name from OOTB
What i'm getting at is that Tim noted he's selecting a Customer Internal in one RiP and Customer External in another, but both relationships are setting Customer Type into the same field.
Therefore when you set one, it is changing the expected BO Type of the other relationship. Suddenly, it can't find that other relationship - That RecID doesn't exist under that type. The relationship is still loaded and hasn't cleared yet, though there is no value found for the display name because it can't find a customer with the type and recID values there after the other relationship has changed the Type. Public ID doesn't get found, then, and defaults to 'Record' (Hence my question about the public ID).
On reload of the record, that Customer ID doesn't load a relationship to that Customer Type, and the RiP is blank.
Thanks Doug! Setting the Group Member Type to "Add Manually" in the Alternate Contact relationship fixed the issue. And you were correct about the PublicID for the Customer Group Object being set to 'Full name' Thanks, again, for your help!