CenterWSServerBS

UploadAttachmentRequest

单独附件上传接口

The following routes are available for this service:
POST	/UploadAttachment

**UploadAttachmentRequest** Parameters:
Name	Parameter	Data Type	Required	Description
Attachment	body	AttachmentModel	No

**AttachmentModel** Parameters:
Name	Parameter	Data Type	Required	Description
Table	form	string	No	表名
Data	form	Dictionary<string, string>	No	上传的数据key为字段名，value为字段值(对应表必须字段:CUSTOMID,ITEMNAME,SYSPRIMARYKEY,REPORTNUM...REPORTPSTHSECOND)
Attachment	form	byte[]	No	附件数据（byte[]） dll调用
AttachmentBase64	form	string	No	附件数据（Base64字符串）Http Json调用
CacheKey	form	string	No	附件缓存唯一Key，客户端要保存
Status	form	int	No	附件状态 0：第一段 1：中间段 2：结束端（只有一段传2）

**UploadAttachmentResponse** Parameters:
Name	Parameter	Data Type	Required	Description
IsSucc	form	bool	No	是否成功
FilePath	form	string	No	附件上传后的路径
ErrMsg	form	string	No	失败信息等

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /UploadAttachment HTTP/1.1 
Host: gxzj.service.jyjzqy.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"Attachment":{"Table":"String","Data":{"String":"String"},"Attachment":"AA==","AttachmentBase64":"String","CacheKey":"String","Status":0}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"IsSucc":false,"FilePath":"String","ErrMsg":"String"}