Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following restrictions can apply to this rowset.
Name |
Type |
Description |
---|---|---|
QUERY<350> |
xsd:string |
Given a specific DAX query, if the query contains a measure, the rowset shows each object on which the DAX query has a dependency. |
DATABASE_NAME<351> |
xsd:string |
The name of the database. |
OBJECT_TYPE<352> |
xsd:string |
A string that indicates the type of the object for which dependency analysis is requested. |
OBJECT_CATEGORY<353> |
xsd:string |
A string that specifies the categorization of an object as being about data access versus analysis. The possible values are the following:
Values DATA_ACCESS and ANALYSIS are mutually exclusive. |
KIND<354> |
xsd:string |
A string that specifies the kind of reference that is used to compute the dependency. The possible values are the following:
An M expression is always both a named dependency and a data dependency. A DAX expression can be either or both. Values NAMED_DEPENDENCY and DATA_DEPENDENCY are not mutually exclusive, and many dependencies are both. |
Both OBJECT_CATEGORY and KIND restrictions MUST be satisfied. If either restriction is not satisfied, the schema rowset output is not returned. Dependency is allowed by current OBJECT_CATEGORY and KIND restriction settings as described in the following table.
Restriction |
OBJECT_CATEGORY |
KIND |
||||
---|---|---|---|---|---|---|
Dependency |
DATA_ |
ANALYSIS |
Not present |
DATA_DEPENDENCY |
NAMED_DEPENDENCY |
Not present |
Data and structural (such as hierarchy and relationship) dependency |
|
Yes |
Yes |
Yes |
Yes |
Yes |
Mashup dependency |
Yes |
|
Yes |
Yes |
Yes |
Yes |
Partition with provider data source dependency |
Yes |
|
Yes |
Yes |
Yes |
Yes |
Named dependency |
|
Yes |
Yes |
|
|
Yes |