DOCSLIB.ORG

Odata Services Company

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

PUBLIC

2021-03-09

OData Services

THE BEST RUN

Content

  • 1
  • SAP Cloud for Customer OData API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

  • 2
  • New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What's New in OData API v2 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Add Public Solution Model (PSM) Fields to Standard OData Services. . . . . . . . . . . . . . . . . . . . . . . . 15 Transport Custom OData Services with Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Compatibility Mode for READ Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Support for User-Friendly IDs in Standard OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Constant Values to Function Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
2.1 2.2 2.3 2.4 2.5 2.6

  • 3
  • OData API Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

OData API v2 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 OData API v1 Reference (Deprecated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Account Contact Relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Account EntityType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Appointment Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 BusinessPartner Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 CodeList Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Contextual CodeList Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Contact Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 EMail Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Employee Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 External ID Mapping Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Individual Customer Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Lead Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Sales Lead Entity Type (Deprecated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Opportunity Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 Phone Call Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Product Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Service Request Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Task Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 TimeEntry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 User Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Visit Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Marketing Attributes Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 HTTP Status Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Service Assignment Entity Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
3.1 3.2

OData Services

  • Content
  • 2

PUBLIC

  • 4
  • OData Service Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Creating an OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 Testing an OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
4.1 4.2

567
OData API Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 (Deprecated) Setting Up OData Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 SAP Cloud for Customer OData Developer's Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

  • Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
  • 8

OData Services

Content

PUBLIC

3

1 SAP Cloud for Customer OData API

The SAP Cloud for Customer OData API conforms to OData version 2 specification. The complete list of collections (or data end-points) of SAP Cloud for Customer OData API, are listed in the OData API Reference section of this document.

Related Information

OData Version 2.0 Specification SAP Cloud for Customer OData API 2.0 Reference

  • 1.1
  • Purpose

Use the OData API, to query, read, add, update and delete data from and into SAP Cloud for Customer. This document is a reference point for learning SAP Cloud for Customer OData API. You'll find a short introduction to the capabilities of the OData API as well as information on where to find more details.

1.2 What is OData?

OData (Open Data Protocol) is an OASIS Standard that defines a protocol for building and consuming RESTful APIs, based on the HTTP protocol.

OData differentiates itself from most of the other RESTful APIs, mainly by providing the following:

●●●

Metadata of the entities exposed by the OData service Relationship between the entities within an OData service System and custom query options for retrieving data

The protocol allows filtering data, ordering and paginating of the query results, retrieving number of records, and more. Querying and modifying data is possible in XML (AtomPub) and JSON formats.

For more information on OData protocol, please visit to http://www.odata.org, where you can find different versions of OData specifications, community resources (such as OData providers and consumer libraries), sample OData services and tutorials.

OData Services

  • SAP Cloud for Customer OData API
  • 4

PUBLIC

Related Information

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata http://www.odata.org/

1.3 Accessing OData API

You can access the SAP Cloud for Customer OData API of your tenant, with the URL pattern: https:// <your_tenant>/sap/c4c/odata/v1/c4codataapi

1.4 Accessing Metadata of the OData API

You can access the metadata of the OData API of your tenant, with the URL pattern: https:// <YourTenant>/sap/c4c/odata/v1/c4codataapi/$metadata

1.5 Authentication

Learn about security options for accessing the SAP Cloud for Customer OData API. Client applications using the OData API, have four options for providing authorization and authentication for their users:

●●●●

Basic Authentication OAuth 2.0 X.509 SAML (Security Assertion Markup Language) based single sign-on.

Using OAuth 2.0 requires a trust relationship to be configured between SAP Cloud for Customer and the identity provider of your client application in the Administrator work center.

See Create Trust Between the Customer Account and SAP Cloud for Customer.

OData Services

SAP Cloud for Customer OData API

PUBLIC

5

1.6 Authorization

Authorization of a business user in the user interface is usually the same as the authorization in OData Services. However, there are some exceptions to this behavior.

Exceptions to Authorization Behavior

See the following table to learn about the exceptions.

Behavior in User Interface

  • Use Case
  • Description
  • (UI)
  • Behavior in OData Service

Work center view is visible without data restriction.
OData service with work center view assigned has full access to all data and operations.

Restriction at Work Center View

Work center view is assigned with no restrictions in the Administrator work center.

Access Restriction at Instance

  • Work center view is assigned Work center view is visible,
  • OData honors RBAM restric-

  • with Read and Write restric-
  • and data visibility is re-

stricted as configured in user access management. tion and limits the access. tion.
Example: Only opportunities

with sales territory 17 are available. Create/Update/ Delete is restricted for opportunities with sales territory 17.
Example: Opportunity with sales territory 17 is restricted Example: User can see op(both Read and Write) for the portunities with sales terri-

  • user.
  • tory 17 only.

Restrictions in Field

  • You can use business roles to The object work list (OWL)
  • OData doesn’t honor field re-

striction and field is visible in response. restrict (Hide/ReadOnly/ UnRestricted) the fields (standard and extension) from the work center views added to business role. doesn’t hide the restricted (hidden) field, but data isn’t displayed.

Thing Inspector UI hides the restricted field.

Example:

ExpectedRevenueAmou

tfield in an opportunity is hidden.

Action Restriction

You can use business roles to UI restricts user from execut- Restriction isn’t honored. It’s

  • restrict business object ac-
  • ing the action.
  • possible to execute the re-

  • tions.
  • stricted function import.

Example: The action Won in Opportunity is restricted for the business role.

  • UI honors KUT adaptations
  • KUT adaptations aren’t hon-

ored.

SAP Key User Tool (KUT) Adaptations

KUT fields with business logic.

Example: KUT field’s visibility based on business role.

OData Services

  • SAP Cloud for Customer OData API
  • 6

PUBLIC

Behavior in User Interface

  • (UI)
  • Use Case
  • Description
  • Behavior in OData Service

UI Switches

UI switches are defined by custom development and can be used to make fields, buttons, or sections of user interfaces hidden, read-only, or mandatory. You can use them to assign a particular version of a UI to a business role and to its affected users.

  • UI switches are honored as
  • UI Switches aren’t honored.

configured.

Data encapsulated within section groups that is hidden via UI switch is available in OData response.

Example: A UI section group is read-only. And another one is hidden.

Enhancements to Authorization Assignment

Authorization assignments for several OData services are enhanced. With this enhancement, users require the necessary authorizations to consume these OData services.

In previous releases, your users may have been able to consume the impacted OData services without the necessary authorization assignments. For those users, this is an incompatible change. As of the August 2020 release, you must assign the work center view assignments as listed in the table for these users.

Here is a list of impacted services:

Authorization As-
Data Workbench Relevant Service signment
OData

Service Name
Entity Type
Entity Type UI Text (La- (Assign at

  • Name
  • bel)
  • least one.)

prcconver- CodPrcsionfactors Conversion- sion Factors

  • Prc Conver-
  • Yes

COD_QUOT E_WCVIEW

Factors

COD_SALE SORDER_W CVIEW

  • prccurren- CodPrcCur- Prc Cur-
  • Yes

COD_QUOT E_WCVIEW

  • cycode-
  • rencyCode- rency Code

  • Names Names
  • names

COD_SALE SORDER_W CVIEW

OData Services

SAP Cloud for Customer OData API

PUBLIC

7

Authorization As-
Data Workbench Relevant Service signment
OData

Service Name
Entity Type
Entity Type UI Text (La- (Assign at

  • Name
  • bel)
  • least one.)

  • prccurren- CodPrcCur- Prc Cur-
  • Yes

Yes Yes Yes Yes Yes

COD_QUOT E_WCVIEW

  • cycodes
  • rencyCodes rency Co-

des

COD_SALE SORDER_W CVIEW

  • prccurren- CodPrc-
  • Prc Cur-

COD_QUOT E_WCVIEW

cydecplaces
CurrDecPlaces rency Decimal Places

COD_SALE SORDER_W CVIEW

  • prccurre-
  • CodPrcE-
  • Prc Ewu-

COD_QUOT E_WCVIEW

  • wukeys
  • wukeys
  • keys

COD_SALE SORDER_W CVIEW

prcexchangerates
CodPrcEx- Prc Ex-

COD_QUOT E_WCVIEW

  • changeR-
  • change

  • Rates
  • ates

COD_SALE SORDER_W CVIEW

prcexchan- CodPrcEx- Prc Exgeratetypes changeRa- change

COD_QUOT E_WCVIEW

  • teTypes
  • Rate Types

COD_SALE SORDER_W CVIEW

prcexpiring- CodPrcExp- Prc Expiring

COD_QUOT E_WCVIEW

  • currencies Curr
  • Currency

COD_SALE SORDER_W CVIEW

OData Services

  • SAP Cloud for Customer OData API
  • 8

PUBLIC

Authorization As-
Data Workbench Relevant Service signment
OData

Service Name
Entity Type
Entity Type UI Text (La- (Assign at

  • Name
  • bel)
  • least one.)

prcobjtypeexpcurr
CodPrcObj- Prc Obj TypExpCurr Type for
Exp Cur-
Yes Yes Yes Yes

COD_QUOT E_WCVIEW

rency

COD_SALE SORDER_W CVIEW

prcquota-

tionprefix

  • CodPrc-
  • Prc Quota-

COD_QUOT E_WCVIEW

Quotation- tion Prefix

Prefix

COD_SALE SORDER_W CVIEW

prcquotations

  • CodPrc-
  • Prc Quota-

COD_QUOT E_WCVIEW

Quotations tions

COD_SALE SORDER_W CVIEW

  • prcwarn-
  • CodPrcWar- Prc Warning

COD_QUOT E_WCVIEW

perexpcurr PerExpCurr Period for
Exp Currency

COD_SALE SORDER_W CVIEW

  • socialme-
  • SocialMe-
  • Social Me- SEOD_SMA Yes

  • diaactivity
  • diaActivity
  • dia Activity

_SADL_WC VIEW

Recommended publications
  • Pyslet Documentation Release 0.6.20160201

    Pyslet Documentation Release 0.6.20160201

    Pyslet Documentation Release 0.6.20160201 Steve Lay February 02, 2016 Contents 1 What’s New? 1 2 Compatibility 7 3 IMS Global Learning Consortium Specifications 13 4 The Open Data Protocol (OData) 101 5 Hypertext Transfer Protocol (RFC2616) 207 6 Other Supporting Standards 247 7 Welcome to Pyslet 357 Python Module Index 359 i ii CHAPTER 1 What’s New? As part of moving towards PEP-8 compliance a number of name changes are being made to methods and class at- tributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names will go away completely. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. Finally, in some cases you are encouraged to derive classes from those defined by Pyslet and to override default method implementations. If you have done this using old-style names you will have to update your method names to prevent ambiguity. I have added code to automatically detect most problems and force fatal errors at runtime on construction, the error messages should explain which methods need to be renamed.
  • ISO/IEC JTC 1 Information Technology

    ISO/IEC JTC 1 Information Technology

    ISO/IEC JTC 1 Information technology Big data Preliminary Report 2014 Our vision Our process To be the world’s leading provider of high Our standards are developed by experts quality, globally relevant International all over the world who work on a Standards through its members and volunteer or part-time basis. We sell stakeholders. International Standards to recover the costs of organizing this process and Our mission making standards widely available. ISO develops high quality voluntary Please respect our licensing terms and International Standards that facilitate copyright to ensure this system remains international exchange of goods and independent. services, support sustainable and equitable economic growth, promote If you would like to contribute to the innovation and protect health, safety development of ISO standards, please and the environment. contact the ISO Member Body in your country: www.iso.org/iso/home/about/iso_ members.htm This document has been prepared by: Copyright protected document ISO/IEC JTC 1, Information technology All rights reserved. Unless otherwise Cover photo credit: ISO/CS, 2015 be reproduced or utilized otherwise in specified,any form noor partby anyof this means, publication electronic may or mechanical, including photocopy, or posting on the internet or intranet, without prior permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester: © ISO 2015, Published in Switzerland Case postale 56 • CH-1211 Geneva 20 Tel.ISO copyright+41 22
  • Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes

    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes

    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, proposes ○ Geodata on the web in raw form. ○ Raw geodata must be searchable How do you find raw geospatial data ? Data Catalogs Wouldn’t it be nice if… And see.. Searchable Raw Geospatial Data www.georest.org Open Data Protocol “The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today.” www.odata.org ODATA HTTP Atom AtomPUB JSON HTTP://.../vancouver/libraries <feed xmlns=http://www.w3.org/2005/Atom … > <title type="text">libraries</title> <id>http://…/vancouver/libraries(10)</id> <title type="text"></title> <entry> <content type="application/xml"> <m:properties> <d:library_name>Britannia</d:library_name> <d:latitude m:type="Edm.Double">49.2756486</d:latitude> <d:longitude m:type="Edm.Double">-123.0737717</d:longitude> <d:address>1661 Napier St</d:address> </m:properties> …..</entry> <entry>…</entry></feed> HTTP://.../vancouver/libraries ?$format=JSON {"d":[{"library_name":"Britannia","latitude":" 49.2756486","longitude":"- 123.0737717","address":"1661 Napier St"} , {..}] } HTTP Header accept: application/json OData Example Live OData Service from Vancouver OData Producers SharePoint 2010, SQL Azure, IBM WebSphere, … GeoREST OData Live Services Netflix, Open Goverment Data Initiative (OGDI), Stack Overflow, Vancouver, Edmonton, … City of Nanaimo OData Consumers Browsers, Odata Explorer, Excel 2010,…
  • SAP Analytics Cloud, Analytics Designer Developer Handbook

    SAP Analytics Cloud, Analytics Designer Developer Handbook

    SAP Analytics Cloud, analytics designer Developer Handbook Document Version: 5.1 – 2020-04-06 Table of Contents 1 Table of Contents Table of Contents ......................................................................................................................... 1 Figures .......................................................................................................................................... 7 1 About Analytics Designer .............................................................................................10 1.1 What Is an Analytic Application? .....................................................................................10 1.2 What Is Analytics Designer? ............................................................................................10 1.3 What Can You Do with Analytic Applications That You Can’t Do with Stories? ..............10 1.4 How Are Stories and Analytic Applications Related to Each Other? ...............................10 1.5 Why Do We Need Both Stories and Analytic Applications? ............................................11 1.6 What Is the Typical Workflow in Creating an Analytic Application? .................................11 1.7 What Are Typical Analytic Applications? .........................................................................12 1.8 How Does Scripting Work in Analytic Applications? ........................................................12 1.9 What’s the Scripting Language for Analytic Applications? ..............................................13 2 Getting
  • Catalogue Open Data Protocol (Odata API) User Guide

    Catalogue Open Data Protocol (Odata API) User Guide

    Catalogue Open Data Protocol (OData API) User Guide Content 1. Introduction .......................................................................................................................................... 3 1.1. Purpose......................................................................................................................... 3 1.2. Change register ............................................................................................................. 3 1.3. Structure of the document ............................................................................................. 3 1.4. Acronyms ...................................................................................................................... 4 1.5. Reference Documents ................................................................................................... 4 2. Open Data Protocol overview ............................................................................................................. 6 2.1. Entity Data Model concept ............................................................................................ 6 Entity Type ..................................................................................................................... 7 Entity Set ....................................................................................................................... 7 3. ONDA OData Entity Data Model ......................................................................................................... 8 3.1. ONDA Entity
  • Deliverable D7.5: Standards and Methodologies Big Data Guidance

    Deliverable D7.5: Standards and Methodologies Big Data Guidance

    Project acronym: BYTE Project title: Big data roadmap and cross-disciplinarY community for addressing socieTal Externalities Grant number: 619551 Programme: Seventh Framework Programme for ICT Objective: ICT-2013.4.2 Scalable data analytics Contract type: Co-ordination and Support Action Start date of project: 01 March 2014 Duration: 36 months Website: www.byte-project.eu Deliverable D7.5: Standards and methodologies big data guidance Author(s): Jarl Magnusson, DNV GL AS Erik Stensrud, DNV GL AS Tore Hartvigsen, DNV GL AS Lorenzo Bigagli, National Research Council of Italy Dissemination level: Public Deliverable type: Final Version: 1.1 Submission date: 26 July 2017 Table of Contents Preface ......................................................................................................................................... 3 Task 7.5 Description ............................................................................................................... 3 Executive summary ..................................................................................................................... 4 1 Introduction ......................................................................................................................... 5 2 Big Data Standards Organizations ...................................................................................... 6 3 Big Data Standards ............................................................................................................. 8 4 Big Data Quality Standards .............................................................................................
  • Blackbaud CRM Query and Export Guide

    Blackbaud CRM Query and Export Guide

    Query and Export Guide 03/23/2016 Blackbaud CRM 4.0 Query and Export US ©2016 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc. The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised of the possibility of damages. In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual and the products it describes at any time, without notice or obligation. All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc. All other products and company names mentioned herein are trademarks of their respective holder. QueryExport-2016 Contents Getting Started with Query 4 Query: A Guided Tour 4 Common Query Fields 20 Common Query Filters 22 Query 25 Information Library 27 Ad-Hoc Queries 27 Smart Queries 58 Selections 71 Copy an Existing Query 74 Export Queries 74 Browse Query Results 75 View Query Results 75 Organize Queries 75 Open Data Protocol (OData) 79 Export 82 Exports 82 Export Definitions 86 Export Process Status Page 100 Import Selections 106 Import Selections 106 Import Selection Process Status Page 110 chapter 1 Getting Started with Query Query: A Guided Tour 4 Common Query Fields 20 Constituent Query Fields 20 Revenue Query Fields 21 Registrant Query Fields 22 Common Query Filters 22 Constituent Query Filters 22 Revenue Query Filters 23 Registrant Query Filters 23 Query is a powerful tool you can use to help filter and group records.
  • Denodo Odata 2.0 Service User Manual

    Denodo Odata 2.0 Service User Manual

    Denodo OData 2.0 Service User Manual Revision 20200508 NOTE This document is confidential and proprietary of Denodo Technologies. No part of this document may be reproduced in any form by any means without prior written authorization of Denodo Technologies. Copyright © 2021 Denodo Technologies Proprietary and Confidential Denodo OData 2.0 Service User Manual 20200508 2 of 34 CONTENTS 1 OVERVIEW........................................................................5 2 INSTALLATION..................................................................6 2.1 DEPLOYING INTO THE DENODO EMBEDDED WEB CONTAINER............8 2.2 CONFIGURING JNDI RESOURCES IN APACHE TOMCAT......................10 3 VIRTUAL DATAPORT PRIVILEGE REQUIREMENTS.................12 4 FEATURES.......................................................................13 5 SERVING METADATA........................................................14 6 QUERYING DATA: THE BASICS..........................................16 6.1 QUERYING COLLECTIONS..............................................................16 6.2 OBTAINING ITEMS BY PRIMARY KEY..............................................16 6.3 ACCESSING INDIVIDUAL PROPERTIES............................................16 6.4 ACCESSING INDIVIDUAL PROPERTY VALUES...................................17 6.5 ACCESSING COMPLEX PROPERTIES...............................................17 6.6 COUNTING ELEMENTS IN A COLLECTION: $COUNT..........................18 6.7 ESTABLISHING RESPONSE FORMAT...............................................18 7 NAVIGATING
  • Information Technology — Open Data Protocol (Odata) V4.0

    Information Technology — Open Data Protocol (Odata) V4.0

    BS ISO/IEC 20802-2:2016 BSI Standards Publication Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06 BS ISO/IEC 20802-2:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 20802-2:2016. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. © The British Standards Institution 2017. Published by BSI Standards Limited 2017 ISBN 978 0 580 90961 0 ICS 35.100.70 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2017. Amendments/corrigenda issued since publication Date Text affected BS ISO/IEC 20802-2:2016 INTERNATIONAL ISO/IEC STANDARD 20802-2 First edition 2016-12-15 Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format Technologies de l'information — Protocole de données ouvertes (OData) v4.0 — Partie 2: Format OData JSON Reference number ISO/IEC 20802-2:2016(E) © ISO/IEC 2016 BS ISO/IEC 20802-2:2016 ISO/IEC 20802-2:2016(E) COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2016 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
  • Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, Mongodb, Odata, Salesforce.Com, Shapefile, and Successfactors Company

    Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, Mongodb, Odata, Salesforce.Com, Shapefile, and Successfactors Company

    PUBLIC SAP Data Services Document Version: 4.2 Support Package 12 (14.2.12.0) – 2020-02-06 Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, MongoDB, OData, Salesforce.com, Shapefile, and SuccessFactors company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 Naming Conventions......................................................... 5 2 Data Services adapters....................................................... 9 2.1 Adapter required knowledge and expertise...........................................11 3 Adapter installation and configuration...........................................12 3.1 Adding an adapter instance.....................................................13 3.2 Adapter Configuration options ...................................................14 JDBC adapter-specific configuration settings......................................19 DP Bridge runtime configuration options.........................................23 HTTP adapter specific configuration settings......................................24 JMS adapter-specific configuration settings.......................................25 3.3 Starting and stopping the adapter instance..........................................27 3.4 Monitoring the adapter instances and operations..................................... 28 3.5 Viewing adapter instance statistics................................................29 4 Creating an adapter datastore................................................. 31 5 Adapter datastore
  • Introducing Odata Data Access for the Web, the Cloud, Mobile Devices, and More

    Introducing Odata Data Access for the Web, the Cloud, Mobile Devices, and More

    David Chappell May 2011 INTRODUCING ODATA DATA ACCESS FOR THE WEB, THE CLOUD, MOBILE DEVICES, AND MORE Sponsored by Microsoft Corporation Copyright © 2011 Chappell & Associates Contents Describing OData ................................................................................................................................................ 3 The Problem: Accessing Diverse Data in a Common Way ......................................................................................3 The Solution: What OData Provides .......................................................................................................................3 How OData Works: Technology Basics ...................................................................................................................5 Using OData: Example Scenarios ......................................................................................................................... 6 Accessing Application Data from Mobile Phones and Web Browsers ....................................................................6 Exposing Data from a Cloud Application ................................................................................................................8 Using Diverse Data Sources with Different BI Tools ...............................................................................................9 Examining OData: A Closer Look at the Technology and Its Implementation .................................................... 10 The OData Data Model .........................................................................................................................................10
  • SAP Crystal Reports Restful Web Services Developer Guide ( PDF)

    SAP Crystal Reports Restful Web Services Developer Guide ( PDF)

    PUBLIC SAP BusinessObjects Business Intelligence platform Document Version: 4.2 Support Package 03 – 2017-05-12 SAP Crystal Reports RESTful Web Services Developer Guide Content 1 Document History..............................................................4 2 Start here....................................................................5 2.1 Introduction to SAP Crystal Reports RESTful web services..................................5 3 RESTful web services fundamentals................................................6 3.1 Making RESTful web service requests.................................................6 Creating the request header.................................................... 10 Creating the request body......................................................12 Interpreting the response header.................................................12 Interpreting a response body in XML format......................................... 14 Interpreting a response body in the JSON format......................................19 Comparison of XML and JSON attributes...........................................24 Working with multilingual data...................................................27 3.2 Retrieving the base URL for RESTful web service requests................................. 28 Retrieving the base URL through the CMC.......................................... 28 Retrieving the base URL programmatically..........................................28 3.3 Authentication................................................................ 29 To get