Search

Why is a custom object field not available on a workspace?

Environment:

Custom objects, Workspaces, All Versions

Issue:

After creating a new custom object, it doesn't appear in the ribbon menus on the incident workspace.

Resolution:

Go to Configuration > Object Designer, expand the package and select the affected custom object. After the object opens, click on Relationships in the ribbon.

In the Object Relationships screen, in the lower side, in the "Children of" section of the object, add a new relationship between the custom object and the object having the workspace where you need to add the fields (usually incidents).

After the object is saved and deployed, open the workspace where you want to add the fields (in this example, the incident workspace). Go to the Insert Field tab and click on the Incident Fields dropdown on the left. Notice that when the menu opens, the newly deployed object will appear among the options. Select the object, and in the ribbon, to the right side of the dropdown menu, a list of all the object's fields will appear so you can drag them onto the incident workspace.

Cause:

These are two possible causes for the object not being available:

1. There is no relationship between the custom object and the incidents object

If no relationship is defined between the two objects, these two tables are not joined in the database, so no fields can be added from one to the other's workspace.

2. The custom object is set as a child of the incidents object

In this case, the fields of the custom object will not be available to be placed on the incident workspace because fields from a child object cannot be used on the workspace of a parent object. If you want to add the fields to the incident workspace, you will need to define the custom object as a parent of the incident object, as described above.

For additional information, refer to the 'Defining relationships' section in the Online Help User Guide documentation. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.