buddyboss/delete-profile-field removes a profile field from the community. confirm_name must match the field name exactly.
What happens to the answers depends on a second confirmation.
Before you run it
Two levels of destruction behind one ability. By default the field disappears and its values survive — recreate the field and the answers come back. Passing confirm_data_loss with the number of members who have answered additionally destroys every one of those answers, permanently. Get the number wrong and the refusal tells you the real one, which is the point: a field that sounds disposable often is not.
At a glance
| Ability | buddyboss/delete-profile-field |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Profiles |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive — removes the field. Stored answers survive unless confirm_data_loss is passed with the correct count. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The default is conservative: the field disappears from profiles and forms, and the stored values stay in the database. Recreate the field and the answers return.
That is genuinely useful. A field retired because it is no longer asked can be brought back without anybody re-entering anything.
Passing confirm_data_loss with the count of members who have answered destroys those answers as well. The count is the check, and getting it wrong produces a refusal that names the real number.
That refusal is the feature. Somebody deleting a field they believe is unused, who is told four hundred people answered it, has learned something before rather than after.
Deleting a whole field group is a larger operation again, with its own ability and its own confirmation.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
field_id | integer | Yes | The field to remove. |
confirm_name | string | Yes | Must match the field name exactly. |
confirm_data_loss | integer | No | The number of members who have answered. Passing it also destroys those answers. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
field_id | integer | The field removed. |
answers_deleted | integer | How many answers went, if any. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Remove the old survey field from profiles.
It resolves to one call:
{
"ability": "buddyboss/delete-profile-field",
"parameters": {
"field_id": 22,
"confirm_name": "How did you hear about us?"
}
}Worth knowing
- By default the answers survive and return if the field is recreated.
- The data-loss count is checked and the refusal names the real number.
- A field that sounds disposable often has hundreds of answers.
- Deleting a group is a separate, larger operation.
Related abilities
- BuddyBoss List Profile Fields — confirm the name and group
- BuddyBoss Delete Profile Field Group — the larger version
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category