Uploading Lookup Values With or Without Canonical Values
Unmapped block is created when canonical code is not present during Lookup creation. The new trackUnidentifiedLookups parameter in RDM tenant configuration has been introduced. This parameter is boolean. By default it has a false value.
Example of RDM Tenant Configuration
Now, in the RDM Tenant Configuration, if the parameter trackUnidentifiedLookups is set to true, then all lookups without canonical code are converted to Unmapped values.
Request to Upload Lookups
Response
Generated unmapped values
Field | Description | Necessary to Create Lookup Value | ||
---|---|---|---|---|
URI | Full URI of Unmapped value. tenantId/type/sourcesystem/code | No | ||
value | Unmappe value | Yes | ||
tenantid | Name of RDM tenant | Yes | ||
updatedBy | ||||
updatedDate | Date of last update | Yes | ||
type | Type of Lookup code | Yes | ||
source | Type of Source System | Yes | ||
code | Lookup code in certain source | Yes | ||
value | Lookup value in certain source | Yes | ||
attributes | List of attribute values associated with type of Lookup code | Yes | ||
name | Attribute name | Yes | ||
value | Attribute value | Yes |
Unmapped Values API
List lookup values for tenant
List Unmapped Values for Tenant by Type
Create Unmapped Value
Get Unmapped Value
Search filters
Filter Properties | Description |
---|---|
type | Lookup type name |
source | Source system |
code | Lookup code |
value | value |
updateDate | last lookup update date |
updatedBy |
Sorting
Same properties as for search filter.
Order | Description |
---|---|
asc | A to Z, 0 to 9 |
desc | Z to A, 9 to 0 |
Filter Operators | Description |
---|---|
equals(property, value) | exact match condition ignoring case |
fullText(property, value) | combines results into the overall result. Any entity whose title field contains at least one of the specified terms will match the query. The more terms that match, the more relevant the entity |
startsWith(property, stricted value) | prefix condition; returns entities that have condition property starting with condition value |
contains(property, tokenized value) |
prefix condition; returns entities that have condition property starting with condition value |
lt(property, value) | 'less than' condition |
lte(property, value) | 'less than or equals' condition |
gt(property, value) | 'greater than' condition |
gte(property, value) | 'greater than' or equals condition |
missing(property) | returns entities with fields that have no values for 'property' or 'property' value is empty |
exists(property) |
returns entities having some value for 'property' |
Facet Search
Facet search uses the Google Search Index to calculate the number of searched records. However, it has limitations according to Query and Sorting Options.
Name | Required | Description |
---|---|---|
facet | No |
Comma-separated list of facets to return. If this parameter is not specified than all facets will be returned. Available facets: source, type |
filter | No |
Support all filter functions and operators as described above |
Get Dependencies by URIs
Get dependencies between lookup types by using multiple URIs.
Delete Unmapped Values by URIs
Use this to delete unmapped values by their URIs (maximum number of URIs that can be deleted is 1000). The response contains an array of results for each URI, where the "success" status indicates that the unmapped values are either deleted successfully or do not exist. In case of an error, an error object is returned.
Delete Unmapped Value
Use this to delete an unmapped value by its type, source system, and code. The response returns the "success" status if the unmapped value is deleted successfully or it does not exist. In case of an error, an error object is returned.