System Administrator Scenarios › How to Create a Custom Object › Review the Prerequisites

Review the Prerequisites

Review the following prerequisites to help ensure that you can successfully create a custom object.

Predefined Setup

This scenario assumes that you have set up the following:

Partitions

Set up partitions if you want to associate the object attributes with a particular partition. Associating object attributes to partitions allows you to create different presentations of the same objects for different users.

Note: For more information about setting up partitions, see the Studio Developer's Guide.

NSQL queries

Create NSQL queries if you plan to use a parameterized lookup. Create the NSQL queries ahead of time so you can map the query parameters to the object.

Note: For more information about setting up partitions, see the Studio Developer's Guide.

Organizational breakdown structure (OBS)

Create your organizational breakdown structure for the following purposes:

• Associating the OBS to your object instances to control access across department hierarchies, and reporting.
• Creating fiscal time-scaled values using the time-varying attribute data type.

Note: For more information about setting up your OBS, see the Administration Guide.

Note: For more information about creating custom fiscal timescale values, see the Studio Developer's Guide.

Lookup attributes definition

Create the lookup that you want to add to a single value or Multi Valued Lookup data type attribute.

Note: For more information about creating lookups, see the Studio Developer's Guide.

Reserved words

When creating an object, do not use the following reserved words for the object name or object ID:

Custom attributes

Consider the following information for custom attributes:

• Verify that the attributes you create meet the needs of your users. Once you create an attribute, you cannot remove it from the object. You can only deactivate it so that it does not display.
• Create only the attributes needed. You can add many custom attributes to an object. However, the number of attributes affects the amount of time it takes to display pages, so do not create more attributes than you need.

Important! The product supports up to 500 custom attributes for each object. However, we strongly recommend that you do not assign more than 100 custom attributes to a single custom object. High numbers of custom attributes for an object may result in performance issues and subsequent upgrades may fail. If you need a large number of custom attributes, consider creating and using a subobject rather than assigning a large number of custom attributes to a single object.

Back to Top