ArticleAttachments

Query and Delete Acticle Attachment in Zendesk.

Table Specific Information

Select

The following queries are processed server side while other filters are processed client side by the connector. Allowed for Agents and End users, as long as they can view the associated article.

SELECT * FROM ArticleAttachments WHERE ArticleId = '18214155815057'
SELECT * FROM ArticleAttachments WHERE Id = '18470148791057'
SELECT * FROM ArticleAttachments WHERE Id = '18470148791057' AND Locale='en-us' AND ArticleId = '18214155815057'

You can turn off the client-side execution of the query by setting SupportEnhancedSQL to false in which case any other search criteria will be ignored and an unfiltered response will be returned.

Delete

You must specify the Id of the ArticleAttachments to delete it. Allowed for agents.

DELETE FROM ArticleAttachments WHERE Id = '18460736594833'

Columns


Name	Type	ReadOnly	References	Description
Id [KEY]	Long	True		Assigned ID when the article attachment is created
ArticleId	Long	True	Articles.Id	The associated article, if present
ContentType	String	True		The file type. Example: image/png
ContentUrl	String	True		URL where the attachment file can be downloaded
CreatedAt	Datetime	True		The time the article attachment was created
DisplayFileName	String	True		display_file_name
FileName	String	True		The file name
Inline	Boolean	True		The attached file is shown in the admin interface for inline attachments. Its URL can be referenced in the article's HTML body. Inline attachments are image files directly embedded in the article body. If false, the attachment is listed in the list of attachments. The default value is false
RelativePath	String	True		relative_path
Size	Integer	True		The attachment file size in bytes
UpdatedAt	Datetime	True		The time the article attachment was last updated
Url	String	True		The URL of the article attachment
AttachmentsResponse	String	True		Content of the attachments

Pseudo-Columns

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.