With SAP CRM Fiori Application, for example . Attachment processing has two levels , That is to say Fiori UI Show attachments on ( Read operation ), And by Fiori UI Create attachments ( Write operation ).

Attachment The read

As shown in the figure below , Click any Attachment Hyperlinks ,

That is, automatically open the browser download window .

It's time to OData Corresponding implementation system , such as AG3 backstage , Things code SEGW, open CRM_OPPORTUNITY OData project , Create a file called Opportunity_Attachments Of association, Point to a name OpportunityAttachment Of Dependent Entity.

Opportunity and OpportunityAttachment The relationship between models is 0:n, That is, a Opportunity It's not allowed to attachment, Multiple attachment.

Attachment Model fields for ：

We can do it in AG3 To set breakpoints , debugging attachment Read requests for ：

Fiori UI Put what you want to read attachment The instance information passes through SAP UI5 Pass the code to the background ABAP：

Last call CL_CRM_OPPORTUNITY_DPC_EXT~GET_STREAM Methods from AG3/001 Read attachment data on the system ：

Fiori The front desk is S3.view.xml It uses UploadCollection Control to display attachments .

When Attachment When the tab is clicked , Trigger attachmentsTabSelected Method ：

In this method , Manual call OData API Initiate reading data to the background OData request ：

var info = this.getView().byId('info');
		var headerGuid = info.getModel('json').getData().Guid;
		var oModel = this.oModel;
		var sPath = this.sPath;
		// get the list to set the post url param
		var that = this.getView();

		oModel.read(sPath, null, [
			"$expand=Attachments"
		], true, jQuery.proxy(function(odata, response) {
			var data = {
				OpportunityAttachments: []
			};
			var length = response.data.Attachments.results.length;

     

      
1.
      
2.
      
3.
      
4.
      
5.
      
6.
      
7.
      
8.
      
9.
      
10.
      
11.
      
12.
      
13.
      
14.
     

Attachment The creation of

Click on + Icon , Choose a file to upload locally ：

SAP UI5 Control can display the uploaded progress bar ：

Trigger the background CL_CRM_OPPORTUNITY_DPC_EXT～CREATE_STREAM Method ：

CREATE_STREAM Method to create a flow ( Media resources ) And corresponding entities ( Media link entries ). Additional information can be found in Slug In the head . The layout of creating media link entries is performed first HTTP Post, It only contains binary data . Be careful , It is not allowed to publish the item itself first , Then release relevant media resources . be based on Slug head , Developers can pass additional information to the server , for example , The server can be used to store binaries ( Media resources ) And create entities ( Media link entries ) Created framework . Newly created entity ( Media link entries ) stay HTTP The response is sent back to the user , The response can be updated with appropriate data . The updated entry will be in HTTP Put Send to SAP NetWeaver Gateway System , To complete the creation of media resources / The process of media link entries .