What is the size of the attachment that is not eligible for cloning?

[Tsutomu Kudo]

The question is about instance cloning.

If [Exclude large attachment data] is checked when creating a clone, What is the size of the attachment that will be excluded from the clone?

And can its file size be changed?

[sushantmalsure · Accepted solution]

Interesting question and I too wonder about it now.

Based on ServiceNow documentation:

Small attachments have table-name values that start with ZZ_.

The attachment data type value indicates that it is a large file such as an application or video.

So I believe thats how in cloning process ServiceNow exclude large attachment data.

[sushantmalsure · Accepted solution]

The name "Exclude large attachment data" is misleading. Large attachments are identified by file type rather than the size.

It actually prevents the cloning of large attachments such as video files, image files, and other typically large binary file types. Excludes all common binary file types, regardless of file size. When selected, the clone also excludes attachments from the Attachments [sys_attachment] and Attachment Documents [sys_attachment_doc] tables that meet all these criteria.

• The attachment table_name value does not indicate it is a small file. Small attachments have table name values that start with ZZ_.
• The attachment data type value indicates it is a large file such as application or video.
• The attachment table_name is not one of these system tables: sys_certificate, ecc_agent_jar, ecc_agent_mib, sys_store_app, or invisible.sys_store_app.

[sushantmalsure · Accepted solution]

Interesting question and I too wonder about it now.

Based on ServiceNow documentation:

Small attachments have table-name values that start with ZZ_.

The attachment data type value indicates that it is a large file such as an application or video.

So I believe thats how in cloning process ServiceNow exclude large attachment data.

[sushantmalsure · Accepted solution]

The name "Exclude large attachment data" is misleading. Large attachments are identified by file type rather than the size.

It actually prevents the cloning of large attachments such as video files, image files, and other typically large binary file types. Excludes all common binary file types, regardless of file size. When selected, the clone also excludes attachments from the Attachments [sys_attachment] and Attachment Documents [sys_attachment_doc] tables that meet all these criteria.

• The attachment table_name value does not indicate it is a small file. Small attachments have table name values that start with ZZ_.
• The attachment data type value indicates it is a large file such as application or video.
• The attachment table_name is not one of these system tables: sys_certificate, ecc_agent_jar, ecc_agent_mib, sys_store_app, or invisible.sys_store_app.

[Tsutomu Kudo · Accepted solution]

I understood that the setting excludes binary files, not file sizes.
Thank you very much.