Invalid Objects

Invalid Objects

 

To ensure the validity of SQL and PL/SQL code for objects in the system, Administrators should check daily for errors on the Invalid Objects page for the following objects:

  • Applets

  • Fields

  • Rules (including HTTP Call Rule) & Rule Packages

  • Reports

  • Dashboards

  • Notifications

  • Workflow Templates

  • Imports (excluding IMP_ENTITY.SQL_TEXT field)

  • PL/SQL Blocks

  • Tenant Parameters

DB packages are not currently available for validation.

 

 

Understanding the Invalid Objects Page

The Invalid Objects page lists all of the objects that include SQL PL/SQL with an error. Administrators should check this page daily. (Best practice is to keep this grid empty. OneVizion revalidates all objects nightly and after an object references rebuild and fills this grid with any objects that fail validation.) See Validating Invalid Objects below to handle objects that display on this page.

To make sure you are aware of “new” invalid objects, you can sort or filter in Quick Search using the Invalid Since column.

Administrators should make a habit of checking this page every time after they rebuild object references because of the likelihood of this causing invalid objects. See Rebuilding Object References on the Admin Object Reference page.

To access the Invalid Objects page, navigate to: Dev Center > Application Process Management > Invalid Objects

image-20240520-183146.png
An Example Invalid Objects Page

Invalid Objects Columns

Invalid Objects Columns

Component Name

Identifies the type of component the object is.

Entity ID

The ID hyperlink that opens the applet for the object.

Entity Name

The name of the entity.

Table

The database table that stores the object

Column

The column of the table that stores the SQL or PL/SQL script of the object

Error Message

Details including where and what is the cause for the error

Invalid Since

The date and time when the nightly job first determined the object to be invalid.

Validation Date

The date and time of the last attempt to validate the field.

Created At

The date the object was created.

Created By

The user who created the object.

Modified At

The date the object was last modified.

Modified By

The user who last modified the Object

 

 

Validating Invalid Objects

For each of the invalid objects on the Invalid Objects page, the Administrator will research the error and fix the issue in the PL/SQL for the object. Then the objects can be validated.

 

Steps to Validate Invalid Objects:

  1. Navigate to Dev Center > Application Process Management > Invalid Objects

  2. For each listed object, examine the error message to understand the issue.

  3. Click the Entity ID hyperlink for the objects.

  4. Make the necessary changes.

  5. Return to the Invalid object page:
    select the object where you made changes and click Validate
    OR
    if you’ve made corrections for all of the objects listed here, click Validate All

  6. When the object is successfully validated, it no longer displays on the Invalid Object page. If all objects are successfully validated, the grid is empty.

 

 


Administration for Invalid Objects

Users need ADMIN_INVALID_OBJECT security group privileges to see and use the Invalid Object data.

R- lets users see data.

E- lets users see and use the Validate and Validate All buttons.

Administration for Invalid Objects

Users need ADMIN_INVALID_OBJECT security group privileges to see and use the Invalid Object data.

R- lets users see data.

E- lets users see and use the Validate and Validate All buttons.