Connector for SAP Gateway in applications

Applications module Integrate external data

1. Create external data group

A connection to an SAP Gateway data source can be used in any Intrexx application. To do so, Select the application node and create a new external data group via the New menu / External data group.


Define the title for the external data group here.

Database connection

The desired connection can be selected here.

Data handler

The appropriate data handler is entered automatically when you select an SAP Gateway connection.

Table/ View

You can enter the name of the table or view directly or click on "Search" and search for name of the table or view in the dialog that opens. Click on "OK" once you have selected your table view.

Click here for more information about the settings for logging in. The data fields, which should be provided by the OData service and displays in applications, can now be selected on the Data fields tab and then linked to application elements.

2. Data types

Click here for more information.

3. References

Click here for more information.

4. Files

4.1. Binary data fields

OData data fields of type Edm.Binary (BLOB) are handled in Intrexx as the File data type. This allows binary data to be stored in Intrexx file fields. Since the file type cannot be automatically detected from the OData binary fields, it must be saved in the expert settings for the data field.

This will automatically be used as the filename extension when the binary data is saved. Currently, only one file type per field can be defined for all data records. For accessing and manipulating files, OData (Version 2.0 or higher) offers Media Link Entries. These are the recommended method for accessing binary data. Another possibility to enable downloading of the contents of binary fields uses the callable method "$OdataMediaResourceCallable.getDownloadURIForBinaryProperty()". This generates a URL, which can be inserted in a download link on an entry or view page:
<a target="_blank" href="$ODataMediaResourceCallable.getDownloadURIForBinaryProperty($ProcessingContext, $DC.getRecId(), '<GUID_DATAGROUP>', '<BINARY_PROPERTY NAME>', '<FILE_NAME>','CONTENT_TYPE', '<DISPOSITION_TYPE>')">Download File</a>
With this method it is possible to define the filenames and content type dynamically, while these values are ascertained from other data fields. Click here for more information. Click here for more information. Click here for more information.

5. OData Function Imports

In addition to access to Entity Collections (tables), OData also provides the ability to define what are known as Function Imports and to run them via the service. Function imports are comparable to stored procedures in database management systems, and can receive input parameters and return a single record or a set of records as the result. Since Intrexx does not offer direct support for stored procedures, the following procedure must be used to call function imports:
  1. By using the service metadata, determine the name of the function to be called(such as with "GetProductsWithRating"), the required input parameters, whether the results consist of a single record (OData entry) or a result set (OData entity set), and the entity type (table in the Intrexx data group) of the results.
  2. Create a view page for the parameters of the function and a further view page to view the results of the function call.
  3. On the view page for the function parameters, place an edit field for each parameter, but do not link these to a data field, and also create a button and set the link destination to the view page containing the results.
  4. On the results page, create a view table (in cases when there is a results set), select the corresponding data group (depending on the function results type), and the data fields to be displayed.
  5. Now switch to the Expert tab of the view table properties and define the following settings:
      Function name (from the service metadata)
    • odata.functionImport.parameterFieldGuid
      List of field GUIDs for the function parameters.
    • odata.functionImport.parameterName
      List of parameter names (from the service metadata)
Please note that the order of field GUIDs and parameter names in the two lists must match exactly.

Click here for more information about the expert settings.

6. More information

System requirements
Consume SAP Gateway data
Export / Import