> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/delete-a-calculated-field.md).

# 計算フィールドを削除する

ユーザー作成 [計算フィールド](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/calculated-fields-explained.md) 計算の使用を継続したくない場合は削除できます。

{% hint style="warning" %}
**警告:** 計算フィールドの削除は永続的で、元に戻せません。
{% endhint %}

1. 左側のナビゲーションメニューで、次を選択します ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → データソース** → **フィールド**.
2. の *フィールド* テーブルで、削除したい計算フィールドを見つけます。
3. 計算フィールドにカーソルを合わせて、次を選択します **削除**.
4. ポップアップを確認し、続行することを確定してください。

#### 計算フィールドを削除した場合の影響

削除された計算フィールドは、フィールドテーブルに引き続き表示されます。計算フィールドに固定またはスライド式の [トラッキングウィンドウ](/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/tracking-windows-for-calculated-fields-explained.md)の場合、過去の計算結果も個々の参加者プロフィールに表示されることがあります。

| もし            | 次に                                     |
| ------------- | -------------------------------------- |
| トラッキングウィンドウなし | 削除されたフィールドは、値が固定された状態で参加者のプロフィールに残ります。 |
| トラッキングウィンドウ   | 削除されたフィールドは、参加者のプロフィールから直ちに削除されます。     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/delete-a-calculated-field.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.