> 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/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/recalculate-a-calculated-field.md).

# 重新计算计算字段

设置新的计算字段时，我们只会在收到符合计算条件的新事件数据时执行计算。重新计算是一种可选方式，可用于对历史事件数据执行计算。重新计算历史数据会更新参与者的个人资料，但不会触发您的项目规则运行，因此您可以放心重新计算，不会影响您的项目。

#### 开始重新计算

设置或编辑使用以下任一种计算方式的计算字段时，您可以请求重新计算： `sum` 或 `count` 。

1. 在左侧导航菜单中，选择 ![](https://impact-1.gitbook.io/docs/emvxfLrwrlacc4y3y02Y/~gitbook/image?url=https%3A%2F%2F4048883401-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FwMLlMoFBtKJa8ptd3zaw%252Fuploads%252Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%252Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg%3Falt%3Dmedia\&width=300\&dpr=3\&quality=100\&sign=71dd50ef\&sv=2) **\[Engage] → 数据源 → 字段**.
2. 打开字段创建界面。
   * 要创建新的计算字段，请选择 **创建计算字段**.
   * 要编辑现有的计算字段，请在 *字段* 表格中找到该字段。将光标悬停在该字段上，然后选择 **编辑**.
3. 在 *审核* 部分中，选中 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **保存时重新计算值** 复选框。
4. 选择 **保存**.

{% hint style="info" %}
**重新计算示例：** 现在是 9 月 26 日。您正在设置一个固定 1 个月的计算字段 [跟踪窗口](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/tracking-windows-for-calculated-fields-explained.md)。您不希望该字段仅从 26 日开始计算到月底，而是希望将整个 9 月的数值都纳入计算。设置字段时，您可以选中 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[未选中的复选框]** **回填计算** 复选框来实现这一点。保存更改后，重新计算便会开始。
{% endhint %}

#### 处理顺序

{% hint style="info" %}
**事件处理顺序：** 重新计算期间，事件的处理顺序可能会发生变化。仅当排队中的事件正在处理时我们收到新的事件数据，才会出现这种情况。
{% endhint %}

重新计算不会立即完成，所需时间取决于待处理的数据量。您可以在 ![](https://impact-1.gitbook.io/docs/emvxfLrwrlacc4y3y02Y/~gitbook/image?url=https%3A%2F%2F4048883401-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FwMLlMoFBtKJa8ptd3zaw%252Fuploads%252Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%252Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg%3Falt%3Dmedia\&width=300\&dpr=3\&quality=100\&sign=71dd50ef\&sv=2) **\[Engage] → 数据源 → 处理任务页面**.

重新计算进行期间收到的任何事件都会进入队列，直至重新计算完成。重新计算完成后，我们会按照收到事件的顺序开始处理这些事件。


---

# 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/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participants/custom-and-calculated-fields/recalculate-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.
