Field Update Exceptions
To effectively balance user flexibility with robust data validation and structural integrity, the OneVizion Platform places some restrictions on the user’s ability to update fields.
While the platform does include some visual cues for what can be updated (cursor turns into hand pointer) and what cannot be updated (cursor remains arrow pointer, grayed field indicates read-only, lock icon indicates field is locked) the following information can help to understand any restrictions.
Field Update Exceptions
Primary Key Fields: These unique identifiers are read-only to preserve the foundational structure of the data.
Relationship Fields: Fields establishing links between different data entities are locked to prevent inadvertent disruption of data relationships.
Read-Only and Locked Fields: Certain fields are explicitly designated as read-only (grey background) or locked (lock icon) due to their nature (e.g., system-generated values, audit trails) or specific business rules.
Security Role Restrictions: Field access and editability can also be restricted based on the user's assigned security role. If a user's role doesn't grant them access to a particular field, they won't be able to view or interact with it. This ensures that users only see and interact with the data relevant and permissible to their role.
Limits for Dynamic Cascading Fields
When a field is setup as a Cascading Field, its editability is dynamically determined by the values of other dependent fields. When a field's value is derived from or controlled by another, it automatically becomes non-editable, ensuring data coherence across related entries. For clarity, such fields display a message label: "This field is disabled because the following dependent fields are locked: 'FIELD_NAME'".
Limits for (Excel-Like) Copy to Adjacent Cell(s) Feature
To enhance user productivity, our grid incorporates an "Excel-like" fill-down feature. This allows users to quickly populate multiple fields by dragging the corner of a source cell, replicating its value into adjacent cells. Crucially, this functionality is specifically not applicable to the following field types, maintaining data integrity and adherence to their specific constraints:
Primary Key Fields: As unique identifiers, their values can't be replicated or filled down.
Relationship Fields: These fields define critical links between data entities and can't be bulk-filled.
Read-Only and Locked Fields: Their non-editable nature inherently prevents the use of the fill-down feature.
Database-Dropdown Fields: While offering predefined options, these fields aren't eligible for the drag-and-fill operation to prevent invalid or unintended selections.
Cascading Fields: Since their values are dynamically determined by other fields, cascading fields themselves can't be filled down, nor can their dependent fields be filled in this manner, to ensure the integrity of the cascading logic.
