Contents
The following query returns task records and expands the related contact, the account related to the contact, and finally to the systemuser who created the account record. If you expand on collection-valued navigation parameters to retrieve related entities for entity sets, only one level of depth is returned if there is data.
How to retrieve a collection of related records?
If you want to retrieve the collection separately, you can use the value of the @odata.nextLink property with a new GET request to return the required data. The following example retrieves the tasks assigned to the top 2 account records. One has related tasks, the other does not.
In either case an @odata.nextLink property will be returned for the related entities. If you want to retrieve the collection separately, you can use the value of the @odata.nextLink property with a new GET request to return the required data.
How to query related records in Microsoft Excel?
If you include only the name of the navigation property, you’ll receive all the properties for related records. You can limit the properties returned for related records using the $select system query option in parentheses after the navigation property name. Use this for both single-valued and collection-valued navigation properties.
See Developers: Understand terminology in Microsoft Dataverse. Use the $expand system query option in the navigation properties to control what data from related entities is returned. There are two types of navigation properties:
When to use accountid over account.id?
If your AccountId is actually populated with the Id of the Account record, you should get a return value from: Note that it is preferable to use AccountId over Account.Id. You also don’t need to filter your subquery if you go that route. Again, if the lookup is populated, you should see results:
When did associate contacts with multiple accounts come out?
After clarifying in a comment on your question, we’re working with the Associate Contacts with Multiple Accounts feature, which was made generally available in Summer ’16 (API v37.0)
How is a count represented in an API?
As an API consumer, I would expect each count value to be represented either as a subresource to the countable resource (i.e. GET /tasks/count for a count of tasks), or as a field in a bigger aggregation of metadata related to the concerned resource (i.e. GET /tasks/metadata).
What should be included in response to / API / users?
While the response to /API/users is paged and returns only 30, records, there’s nothing preventing you from including in the response also the total number of records, and other relevant info, like the page size, the page number/offset, etc. The StackOverflow API is a good example of that same design.