Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Requested DisplayField : reqCandStatus for entity type requisition does not exist — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Requested DisplayField : reqCandStatus for entity type requisition does not exist

Question
5
Views
0
Comments
edited Jun 3, 2012 8:30PM in Technical Topics (TBE)

Content

I'm viewing the list of fields for the requisition entity. One of the available fields is:

[6] => stdClass Object

                        (

                            [name] => reqCandStatus

                            [label] => Candidate Status

                            [isCustom] =>

                            [dataType] => Picklist

                            [isSearchable] => 1

                            [isRequired] =>

                            [isReadOnly] =>

                            [description] =>

                            [maxLength] => N/A

                        )

The documentation labels each object field as follows:

"fields":[

{

"name":"<<OBJECT_FIELD_EXTERNAL-API_NAME>>",

"label":"<<OBJECT_FIELD_GUI-LABEL_FIELD_NAME>>",

"isCustom":><<OBJECT_FIELD_CUSTOM-OR-STANDARD_BOOLEAN-VALUE>>”,

"dataType":"<<OBJECT_FIELD_FIELD-TYPE>>",

"isSearchable":<<OBJECT_FIELD_SEARCHABLE_BOOLEAN-VALUE>>,

"isRequired":<<OBJECT_FIELD_REQUIRED-OR-NOT_BOOLEAN-VALUE>>,

"isReadOnly":<<OBJECT_FIELD_EDITABLE-OR-NOT_BOOLEAN-VALUE>>,

"description":"<<OBJECT_FIELD_DESCRIPTION-VALUE>>"

}

]

So it looks like the "name" is called OBJECT_FIELD_EXTERNAL-API_NAME.

This field is also of type "Picklist".

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!