Getting Started With Dictionary-Based Custom Properties

Last Updated: Jun 03, 2019 05:51AM PDT
Customer Properties Administration

Defined custom properties can now be marked as required during registration, their values be given a data type that should be conformed to and optionally specify a list of values to be limited to.

As of now, the list of values is stored as strings and the entered list of values are not checked against the data type selected or any data format pattern (it is up to the user to ensure they match).  The data format is a free form text of 100 characters.

Custom Properties keys (or names) can be defined in dictionary admin (hereby referred to as defined custom properties). A key can be associated with one of 5 object types (entity, batch, assay result, sample, shipping).

Changing the name or deleting a name has no effect on properties that are already attached to existing objects. They simply become undefined custom properties. Similarly adding a name makes existing custom properties of the same name to be become defined custom properties.

Custom Properties Search

You can search for project data results that have defined custom properties. The search UI was modified to specify what custom property to search for, the type of search (full value or partial value) and the value to search for.  All custom properties defined in the administration dictionary UI are displayed in the property combo boxes.

With a simple search, you can specify one custom property per object type. To search for results with more than one custom property of the same type, you can use the advanced query functionality.
The full value search (“=”) does an case insensitive search for the full value. The partial search (“contains”) does a case insensitive search where the value specified matches either the full value or is contained in the matching value.

Entity and batch custom property search:

Assay, sample, and/or shipping custom property search:

Custom Properties Single View

Single view was modified to display defined custom properties as additional sections/table columns. Custom properties that are not defined show up in tooltips as it currently exists in production.
When an object type does not have custom properties, the section or the table columns are hidden, allowing for space to be better utilized.

Custom Properties Export

Defined and undefined custom properties can now be exported. Defined custom property names show as individual rows in the field column of the export window. Undefined custom properties can be exported by selecting the field {objecttype} Custom properties.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found