Setting Properties for New Data Service Operations This page last changed on Feb 14, 2008. ## Setting Properties for New Data Service Operations Each new entity data service is created with a Read function that contains all the metadata elements identified during data service creation. It can be thought of as comparable to the following construct in the relational world:
    select * from <table>
- Use the Properties dialog to: Optionally modify the operation name. Set the Public option (check if you want your function to be available to client applications). Set the kind of operation (in some cases only Read will be available). Set the Primary option (check if you want your function to be the primary of its type).
  | In some cases this option may not be available.
Select a common XML namespace for the entire data service or individual target namespaces for specific operations. Set the target namespace. The root element, which is read-only, is also displayed.
| Initially the root element name matches the name of the data service.
- ##### Setting Properties for New Data Service Functions ### Default Naming Conventions There are several default naming conventions associated with new data services: When a table, view, or other data source object is the source for a data service, the nominated name is wherever possible the same as the source object name. In some cases, however, names are adjusted to conform with XML naming conventions. Initially the root element name matches the name of the data service.
  | XML Name Conversion Considerations

Document generated by Confluence on Jan 13, 2009 15:57