Det här innehållet finns inte tillgängligt på ditt språk men här finns den engelska versionen,

Det här ämnet har inte bedömts ännu - Bedöm det här ämnet

Windows Azure AD Graph Release Notes

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

July 2012 Release Notes

The following are known limitation issues in the current release.

Not supported:

$count
$expand
$inlinecount
$orderby
$skip (however, $skipToken is supported)
$select; the following portion of the return error message should be ignored "To enable this functionality, set the DataServiceConfiguration. AcceptProjectionRequests property to true."
Queries for Role objects do not support either $filter or $top
Queries for SubscribedSku objects do not support $filter or $top
Paging for link searches (for example, group membership) is not supported. Therefore, skiptokens returned by Group membership queries will fail.

$filter operation limitations:

Paging: Only the first N results are returned, where N is either equal to default page size of 100 or a client-specified page size between 1 and 999. Getting subsequent pages is not possible for filtered searches (in other words, only the first page is returned).
Logical Operator: AND is supported to combine two $filter operands, but OR is not currently supported.
Only the following comparison operators are supported:
- Eq: Equal to.
- le: Less than or equal to.
- ge: Greater than or equal to.

The following Directory object properties are acceptable for $filter queries:

Contact
- City
- Country
- Department
- DirSyncEnabled
- DisplayName
- GivenName
- JobTitle
- LastDirSyncTime
- Mail
- State
- Surname
Group
- DirSyncEnabled
- DisplayName
- LastDirSyncTime
- Mail
- SecurityEnabled
User
- AccountEnabled
- City
- Country
- Department
- DisplayName
- GivenName
- JobTitle
- LastDirSyncTime
- Mail
- State
- Surname
- UsageLocation
- UserPrincipalName

Values: Null values are not acceptable as a $filter value. Otherwise, standard OData values are accepted. Not supported: Arithmetic operators, functions of any kind, and other similar examples.

Other Information:

For reading specific resources (for example, Groups(‘GROUP_ID’)), the following is noteworthy:
- All resources use the “ObjectReference” string-valued property to support lookups (for example, ‘User_guid’ or ‘Group_guid’).
- All resources accept an ObjectId-based identifier value as ObjectReference. The exception is SubscribedSku resources which have an ObjectReference value in the form of “AccountId_SkuId”
- Users additionally support UserPrincipalName as a ObjectReference lookup value.
Queries for all users (in other words, “listing”) are sorted by UserPrincipalName. The other list queries are unsorted.
Reads of specific objects can be done from DirectoryObjects and ReferencedObjects, but no searches whatsoever are allowed.

Var detta till hjälp? Ja Ingen

Inte korrekt

Inte tillräckligt djuplodande

Behöver fler kodexempel

Översättningen behöver förbättras

(1500 tecken kvar)