A Link annotation must have an associated action, destination, or named destination specifying what should happen when the annotation is activated. When merging documents with invalid Link annotations, an ArgumentException is thrown with the message 'Value cannot be null. Parameter name: namedDestination'

Workaround: Remove the invalid annotations:

foreach (var annotation in document.Annotations.ToList())
{
    var link = annotation as Link;
    if (link != null && link.Action == null && link.Destination == null && link.NamedDestination == null)
    {
        (annotation.Parent as RadFixedPage).Annotations.Remove(annotation);
    }
}

Typically, it is the text to be displayed for the annotation or, if the annotation does not display text, an alternate description of the annotation’s contents in human-readable form.

This item will be closed as its subject is too broad. Please refer to the information below for the individual markup annotations.

As of now, the currently supported markup annotations are:

Text
Line
Highlight
Underline
Squiggly
StrikeOut
Stamp

The unsupported annotations and their respective feedback items are:

FreeText
Square
Circle
Polygon
PolyLine
Caret
Ink
FileAttachment
Sound

Adding a table with the same code leads to different results 

When adding 10 identical tables onе or more have missing rows at the bottom. The seems to be caused by the text measurement. 

When importing such documents an InvalidDataException (Unknown compression method <method-name>) is thrown.

According to the current .ZIP File Format Specification these methods are 7, 11, 13, 15, and 17.

Compression method:

PDF / X: the X stands for exchange; a PDF / X document can in principle be processed by any printing company. This means, for example, that only CMYK colors may be used, that all fonts must be present in the PDF, that the document must not be encrypted, and so on.

With the current implementation, the Standard Fonts preloaded in the FontsRepository cannot be replaced.

Attempting to open a Pdf document containing an unsupported action type results in a NotSupportedActionException being thrown (see PdfProcessing: Add support for actions of type Launch).

Can the behavior be changed to ignore unsupported actions and allow the document to be opened?

With the current implementation, the Trigger Events are skippet on import.

From the PDF Specification: An annotation, page object, or interactive form field may include an entry named AA that specifies an additional-actions dictionary that extends the set of events that can trigger the execution of an action.