When there is more than one "picker" dialog to set values for references (parent/child) in a "full" mode for a Cobalt Type object, the last one in the page determines what type of object will be displayed for ALL the pickers in the page. This is because they are using the record id to identify the modal picker object, rather than the field id, so all modal dialogs for the page have the same context.
So, for example, if there is a Type A, that has references to Types B and C, then in the "full" view of the Type A object, both the dialog for choosing Type B objects and the dialog for choosing Type C objects will show the same thing (Type C objects, because that is the last type listed in the "full" mode page).
We have a product to deliver in 2 weeks time that absolutely depends on this working correctly, so this is CRITICAL for our product.
Problem
Announcement
Conversation
Idea
Praise
Question
Open
When there is more than one "picker" dialog to set values for references (parent/child) in a "full" mode for a Cobalt Type object, the last one in the page determines what type of object will be displayed for ALL the pickers in the page. This is because they are using the record id to identify the modal picker object, rather than the field id, so all modal dialogs for the page have the same context.
So, for example, if there is a Type A, that has references to Types B and C, then in the "full" view of the Type A object, both the dialog for choosing Type B objects and the dialog for choosing Type C objects will show the same thing (Type C objects, because that is the last type listed in the "full" mode page).
We have a product to deliver in 2 weeks time that absolutely depends on this working correctly, so this is CRITICAL for our product.