Data service

Data from one or several API transactions is retrieved by a data service. Through a data service, you can copy, retrieve, update, or delete data. You can also use API transactions in sequence. This means that you can use a transaction’s output as another transaction's input.

M3 Experience Designer has these types of data services:

• MI: M3 API programs with transactions to list, get, select, update, delete, add, and copy data. M3 API programs is used to display data using either filter only or selection only, both filter and selection, or M3 functional search as input. If you have created XtendM3 API programs, select MI as the type to find them in the list of available API programs.
• LISTMI: An API program with a generic list transaction that supports the programs listed in 'List and Printer programs. Configure' (CMS005) and 'Information Browser Category. Open' (CMS010). LISTMI is used to display data using either filter only or selection only, both filter and selection, or M3 functional search as input.
• API Gateway: Select this to use API programs available in the API Gateway.
  Note: We only support API suites with versions OAS 3.0 or later.
• There are functionalities in OAS 3.0 that we do not support. These are the examples of what we do not support:
  • API suites with Swagger 2.0.
  • Nested objects when handling API input.
  • Displaying data from different locations in nested objects.
  • Document handling.
  • Language handling.
  • Data formats that are not YYYYMMDD.
  • Time stamps
  • Metadata such as style, explode, allow reserved, enum.