> Documentation index: https://www.gooddata.ai/docs/gooddata-ui/llms.txt lists every page of these docs as Markdown.

# Execute()

- Package: [@gooddata/sdk-ui](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui/index.md)
- Kind: function
- Source: https://github.com/gooddata/gooddata-ui-sdk/blob/rel/11.64/libs/sdk-ui/src/execution/Execute.tsx
- Guides: [Execute](https://www.gooddata.ai/docs/gooddata-ui/latest/data-layer/execute/index.md)

The executor provides a more curated experience to obtain and work with data from backends.

**Signature:**

```typescript
export declare function Execute(props: IExecuteProps): import("react/jsx-runtime").JSX.Element;
```

## Parameters

| Parameter | Type | Description |
| --- | --- | --- |
| props | [IExecuteProps](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui/sdk-ui.iexecuteprops/index.md) |  |

**Returns:**

import("react/jsx-runtime").JSX.Element

## Remarks

It is aligned with the `DataAccess` infrastructure which exposes the underlying data as data series that can be sliced by additional attributes.

Once the executor finishes, the [DataViewFacade.data()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui/sdk-ui.dataviewfacade/index.md#dataviewfacadedata) method will expose the data as series and slices according to the specification to the executor. Note that if the resulting data is empty this will NOT throw a NoDataError. It is the responsibility of the child component to handle that if they need to.

See [IDataAccessMethods](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui/sdk-ui.idataaccessmethods/index.md) for additional documentation