RELATIVITY CERTIFIED ADMINISTRATOR LATEST 2026
EXAM QUESTIONS AND SOLUTIONS GUARANTEE A+
✔✔RDC Import Error: A document with identifier <document identifier> already exists in
the system - ✔✔Fix: The identifier field already exists in the system. You need to do an
overlay to overwrite the existing data.
✔✔RDC Import Error: This file identifier exists attached to another document with
selected key field {0} - ✔✔Fix: Same ID trying to load twice.
✔✔RDC Import Error: This file identifier exists attached to another document with
selected ArtifactID {0} - ✔✔Fix: Same ID trying to load twice.
✔✔RDC Import Error: This file identifier exists attached to another document - ✔✔Fix:
Duplicate page ID in a different document.
✔✔RDC Import Error: Document is already in the selected production - ✔✔Fix: The
Bates number is already loaded.
Because you can't overlay into an existing production, you must create a new
production or replace the images manually on the back end.
✔✔RDC Import Error: This document contains redactions or highlights that can't be
overwritten - ✔✔Fix: Delete the markups.
✔✔RDC Import Error: There is no image specified on this line - ✔✔Fix: Make sure
image id is present in load file.
✔✔RDC Import Error: One of the files specified for this document does not exist -
✔✔Fix: Make sure image files are present for represented path.
✔✔RDC Import Error: The image file specified is not a supported format in Relativity -
✔✔Fix: This can't be loaded without conversion to an approved format.
✔✔RDC Import Error: The file being uploaded is empty - ✔✔Fix: No data exists in the
file so it can't be loaded.
✔✔RDC Import Error: The identifier field for this row is either empty or unmapped -
✔✔Fix: Verify that an identifier exists.
,✔✔RDC Import Error: The identifier specified on this line has been previously specified
in the file - ✔✔Fix: Make sure the identifier field is unique or overlay data.
✔✔RDC Import Error: The document specified has been secured for editing. - ✔✔Fix:
Change security permissions to allow document edit rights.
✔✔RDC Import Error: Your account does not have rights to add a document or object to
this case - ✔✔Fix: Change security permissions to allow document add rights.
✔✔RDC Import Error: A non-unique associated object is specified for this new object. -
✔✔Fix: Two objects with the same name exist in the workspace. Identify the duplicates
and change one of their names.
✔✔RDC Import Error: Your account does not have rights to add an associated object to
the current object. - ✔✔Fix: Change security permissions to allow updates to object.
✔✔RDC Import Error: An object field references a child object which does not exist. -
✔✔Fix: Add a child object.
✔✔RDC Import Error: This record's Overlay Identifier is shared by multiple documents
in the case, and cannot be imported. - ✔✔Fix: Use a unique ID to overlay the data
✔✔Process for overlaying translated text via RDC - ✔✔(1) Create long text field,
available in viewer, and included in Text index (this controls whether it is included in
Keyword index)
(2) Overlay the translated text from the load file into new field
(3) Add this field to an existing dtSearch index and rebuild
(4) Configure workspace to display both the translated and original text - using a synced
standalone window
✔✔Minimum Threading Requirements - ✔✔Document must have the Email From field
and at least one of the following:
Sent Date
Email To
Email Subject
Email CC
Email BCC
These fields can either be in the metadata or in the extracted text.
If a document is recognized as an email and does not have a Date Sent field, it will be
categorized as a draft.
✔✔<Structured Analytics Set prefix>::Email Author Date ID - ✔✔contains a string of
hashes that corresponds to each email segment of the current document's email
,conversation. Each hash is the generated MD5 hash value of the email segment's
normalized author field and the date field. The email thread visualization (ETV) tool
uses this field to create the visual depiction of email threading. For more information,
see Email thread visualization.
✔✔<Structured Analytics Set prefix>::Email Threading ID - ✔✔indicates which
conversation an email belongs to and where in that conversation it occurred. This field
groups all emails into their email thread groups and identifies each email document's
position within the group by Sent Date, beginning with the oldest.
The Email Threading ID format is:
The first nine characters represent the email thread group and root node of the email
thread group tree. This is always a letter followed by eight hexadecimal digits.
The next character is either a + (plus) sign or a - (minus) sign. The + sign means that an
actual root email document exists in the data set provided, and the - sign means that
the root email is not in the data set. For example, an Email Threading ID of "F00000abc-
" indicates that the Analytics engine found evidence of a root email for the email thread
group, but it did not find the root email itself as a separate document in the data set. In
these cases, reviewers may be able to read the text of the missing root email by looking
at the bottom segment of later emails in the thread.
The next characters are zero or more node identifiers. These identifiers are each made
of four hexadecimal digits, followed by a + or - sign that indicates whether the email for
that node exists within the data set. Each identifier defines one node in the tree. For
example, an email sent from A to B, then replied to by B, would have the initial ten
characters for the root message from A to B, plus one five-character set for the reply.
Note: Each email threading node, including the root node, represents one email. The
node contains all copies of the email, even if the email was sent to multiple people in
the data set.
✔✔<Structured Analytics Set prefix>::Email Thread Group - ✔✔initial nine characters of
the email threading ID. This value is the same for all members of an email thread group
which are all of the replies, forwards, and attachments following an initial sent email.
This field is not relational.
✔✔<Structured Analytics Set prefix>::Email Action - ✔✔the action the sender of the
email performed to generate this email. Email threading records one of the following
action values:
SEND
REPLY
REPLY-ALL
FORWARD
DRAFT
✔✔<Structured Analytics Set prefix>::Indentation - ✔✔a whole number field indicating
when the document was created within the thread. This is derived from the # of
Segments Analytics engine metadata field.
, Note: In cases where email segments are modified, for example, a confidentiality footer
is inserted, the Email Threading ID may have a greater number of blocks than segments
in the email. In such cases, the Indentation will reflect the actual number of found
segments in the document. See Indentation levels and the email threading ID.
✔✔<Structured Analytics Set prefix>::Email Threading Display - ✔✔visualization of the
properties of a document including the following:
Sender
Email subject
File type icon, accounting for email action
Indentation level number bubble
The Email Threading Display field also indicates which emails are both inclusive and
non-duplicate by displaying the indentation level number bubble in black.
✔✔<Structured Analytics Set prefix>::Inclusive Email - ✔✔inclusive email indicator. An
inclusive email message contains the most complete prior message content and lets
you bypass redundant content. Reviewing documents specified as inclusive and
ignoring duplicates covers all authored content in an email thread group.
✔✔<Structured Analytics Set prefix>::Inclusive Reason - ✔✔lists the reasons a
message is marked inclusive. Each reason indicates the type of review required for the
inclusive email:
Message—the message contains content in the email body requiring review.
Attachment—the message contains an attachment that requires review. The rest of the
content does not necessarily require review.
Inferred match—email threading identified the message as part of a thread where the
header information matches with the rest of the conversation, but the body is different.
This reason only occurs on the root email of a thread and is often caused by mail
servers inserting confidentiality footers in a reply. Review to verify the message actually
belongs to the conversation.
Unanalyzed Attachment—the message contains attachments that could not be
analyzed by the Analytics engine. In most cases this is due to the attachment being
larger than 30 MB.
✔✔<Structured Analytics Set prefix>::Email Duplicate Spare - ✔✔this Yes/No field
indicates whether an email is a duplicate. Duplicate spare refers to a message that is an
exact duplicate of another message such as a newsletter sent to a distribution list. A No
value in this field indicates that an email is either not a duplicate of any other emails in
the set, or that it is the primary email in the Email Duplicate group. The primary email is
usually the email with the lowest Document Identifier/Control Number, identifier field in
Relativity. A Yes value indicates the document is in an Email Duplicate group, but it is
not the primary document.
✔✔<Structured Analytics Set prefix>::Email Duplicate ID - ✔✔this field contains a
unique identifier only if the email is a duplicate of another email in the set. If the email is
not a part of an email duplicate group, this field is not set.
EXAM QUESTIONS AND SOLUTIONS GUARANTEE A+
✔✔RDC Import Error: A document with identifier <document identifier> already exists in
the system - ✔✔Fix: The identifier field already exists in the system. You need to do an
overlay to overwrite the existing data.
✔✔RDC Import Error: This file identifier exists attached to another document with
selected key field {0} - ✔✔Fix: Same ID trying to load twice.
✔✔RDC Import Error: This file identifier exists attached to another document with
selected ArtifactID {0} - ✔✔Fix: Same ID trying to load twice.
✔✔RDC Import Error: This file identifier exists attached to another document - ✔✔Fix:
Duplicate page ID in a different document.
✔✔RDC Import Error: Document is already in the selected production - ✔✔Fix: The
Bates number is already loaded.
Because you can't overlay into an existing production, you must create a new
production or replace the images manually on the back end.
✔✔RDC Import Error: This document contains redactions or highlights that can't be
overwritten - ✔✔Fix: Delete the markups.
✔✔RDC Import Error: There is no image specified on this line - ✔✔Fix: Make sure
image id is present in load file.
✔✔RDC Import Error: One of the files specified for this document does not exist -
✔✔Fix: Make sure image files are present for represented path.
✔✔RDC Import Error: The image file specified is not a supported format in Relativity -
✔✔Fix: This can't be loaded without conversion to an approved format.
✔✔RDC Import Error: The file being uploaded is empty - ✔✔Fix: No data exists in the
file so it can't be loaded.
✔✔RDC Import Error: The identifier field for this row is either empty or unmapped -
✔✔Fix: Verify that an identifier exists.
,✔✔RDC Import Error: The identifier specified on this line has been previously specified
in the file - ✔✔Fix: Make sure the identifier field is unique or overlay data.
✔✔RDC Import Error: The document specified has been secured for editing. - ✔✔Fix:
Change security permissions to allow document edit rights.
✔✔RDC Import Error: Your account does not have rights to add a document or object to
this case - ✔✔Fix: Change security permissions to allow document add rights.
✔✔RDC Import Error: A non-unique associated object is specified for this new object. -
✔✔Fix: Two objects with the same name exist in the workspace. Identify the duplicates
and change one of their names.
✔✔RDC Import Error: Your account does not have rights to add an associated object to
the current object. - ✔✔Fix: Change security permissions to allow updates to object.
✔✔RDC Import Error: An object field references a child object which does not exist. -
✔✔Fix: Add a child object.
✔✔RDC Import Error: This record's Overlay Identifier is shared by multiple documents
in the case, and cannot be imported. - ✔✔Fix: Use a unique ID to overlay the data
✔✔Process for overlaying translated text via RDC - ✔✔(1) Create long text field,
available in viewer, and included in Text index (this controls whether it is included in
Keyword index)
(2) Overlay the translated text from the load file into new field
(3) Add this field to an existing dtSearch index and rebuild
(4) Configure workspace to display both the translated and original text - using a synced
standalone window
✔✔Minimum Threading Requirements - ✔✔Document must have the Email From field
and at least one of the following:
Sent Date
Email To
Email Subject
Email CC
Email BCC
These fields can either be in the metadata or in the extracted text.
If a document is recognized as an email and does not have a Date Sent field, it will be
categorized as a draft.
✔✔<Structured Analytics Set prefix>::Email Author Date ID - ✔✔contains a string of
hashes that corresponds to each email segment of the current document's email
,conversation. Each hash is the generated MD5 hash value of the email segment's
normalized author field and the date field. The email thread visualization (ETV) tool
uses this field to create the visual depiction of email threading. For more information,
see Email thread visualization.
✔✔<Structured Analytics Set prefix>::Email Threading ID - ✔✔indicates which
conversation an email belongs to and where in that conversation it occurred. This field
groups all emails into their email thread groups and identifies each email document's
position within the group by Sent Date, beginning with the oldest.
The Email Threading ID format is:
The first nine characters represent the email thread group and root node of the email
thread group tree. This is always a letter followed by eight hexadecimal digits.
The next character is either a + (plus) sign or a - (minus) sign. The + sign means that an
actual root email document exists in the data set provided, and the - sign means that
the root email is not in the data set. For example, an Email Threading ID of "F00000abc-
" indicates that the Analytics engine found evidence of a root email for the email thread
group, but it did not find the root email itself as a separate document in the data set. In
these cases, reviewers may be able to read the text of the missing root email by looking
at the bottom segment of later emails in the thread.
The next characters are zero or more node identifiers. These identifiers are each made
of four hexadecimal digits, followed by a + or - sign that indicates whether the email for
that node exists within the data set. Each identifier defines one node in the tree. For
example, an email sent from A to B, then replied to by B, would have the initial ten
characters for the root message from A to B, plus one five-character set for the reply.
Note: Each email threading node, including the root node, represents one email. The
node contains all copies of the email, even if the email was sent to multiple people in
the data set.
✔✔<Structured Analytics Set prefix>::Email Thread Group - ✔✔initial nine characters of
the email threading ID. This value is the same for all members of an email thread group
which are all of the replies, forwards, and attachments following an initial sent email.
This field is not relational.
✔✔<Structured Analytics Set prefix>::Email Action - ✔✔the action the sender of the
email performed to generate this email. Email threading records one of the following
action values:
SEND
REPLY
REPLY-ALL
FORWARD
DRAFT
✔✔<Structured Analytics Set prefix>::Indentation - ✔✔a whole number field indicating
when the document was created within the thread. This is derived from the # of
Segments Analytics engine metadata field.
, Note: In cases where email segments are modified, for example, a confidentiality footer
is inserted, the Email Threading ID may have a greater number of blocks than segments
in the email. In such cases, the Indentation will reflect the actual number of found
segments in the document. See Indentation levels and the email threading ID.
✔✔<Structured Analytics Set prefix>::Email Threading Display - ✔✔visualization of the
properties of a document including the following:
Sender
Email subject
File type icon, accounting for email action
Indentation level number bubble
The Email Threading Display field also indicates which emails are both inclusive and
non-duplicate by displaying the indentation level number bubble in black.
✔✔<Structured Analytics Set prefix>::Inclusive Email - ✔✔inclusive email indicator. An
inclusive email message contains the most complete prior message content and lets
you bypass redundant content. Reviewing documents specified as inclusive and
ignoring duplicates covers all authored content in an email thread group.
✔✔<Structured Analytics Set prefix>::Inclusive Reason - ✔✔lists the reasons a
message is marked inclusive. Each reason indicates the type of review required for the
inclusive email:
Message—the message contains content in the email body requiring review.
Attachment—the message contains an attachment that requires review. The rest of the
content does not necessarily require review.
Inferred match—email threading identified the message as part of a thread where the
header information matches with the rest of the conversation, but the body is different.
This reason only occurs on the root email of a thread and is often caused by mail
servers inserting confidentiality footers in a reply. Review to verify the message actually
belongs to the conversation.
Unanalyzed Attachment—the message contains attachments that could not be
analyzed by the Analytics engine. In most cases this is due to the attachment being
larger than 30 MB.
✔✔<Structured Analytics Set prefix>::Email Duplicate Spare - ✔✔this Yes/No field
indicates whether an email is a duplicate. Duplicate spare refers to a message that is an
exact duplicate of another message such as a newsletter sent to a distribution list. A No
value in this field indicates that an email is either not a duplicate of any other emails in
the set, or that it is the primary email in the Email Duplicate group. The primary email is
usually the email with the lowest Document Identifier/Control Number, identifier field in
Relativity. A Yes value indicates the document is in an Email Duplicate group, but it is
not the primary document.
✔✔<Structured Analytics Set prefix>::Email Duplicate ID - ✔✔this field contains a
unique identifier only if the email is a duplicate of another email in the set. If the email is
not a part of an email duplicate group, this field is not set.
