I can't update Business Group or Business Product on a tactic

Short Description Trying to change Business Group or Business Product on a tactic produces an error or silently fails to save. The most common causes are workflow references and stale picklist values.

What this article answers

  • The two error patterns you might see and what each means.
  • Step-by-step recovery for each pattern.
  • How dependent custom attributes interact with this edit.

What's happening

You're editing a tactic and need to change Business Group, Business Product, or both. One of these happens:

  • An approval-workflow error blocks the save.
  • The save appears to succeed but the value reverts when you reload.
  • The desired option doesn't appear in the dropdown even though you can see it elsewhere.

[SCREENSHOT NEEDED — Inspection Window with Business Group / Business Product attributes]

Why this happens

Business Group and Business Product are dependent custom attributes — selecting a Business Group filters which Business Products are available. Three things can interfere with saving an edit:

  1. The tactic's Approval Workflow is inactive or deleted. Hive9 blocks all edits on a tactic with an orphaned workflow reference, including dependent-attribute edits.
  2. The new value was recently removed from your source system (for example, an integrated CRM or BU master). The value may still appear in Hive9 because of cached attribute data — but saving it can fail or cause the value to revert.
  3. A custom field dependency was reconfigured. If the Business Group → Business Product dependency was updated, in-flight tactics referencing old combinations may not save cleanly until they're re-aligned.

How to fix it

Step 1 — Check for an approval-workflow error

If you see "Selected Approval Workflow is either marked as inactive or deleted" when you try to save, fix that first. See Error: "Selected Approval Workflow is either marked as inactive or deleted" for the steps.

Once the tactic has an active workflow reference, return to the Business Group / Business Product edit.

Step 2 — Verify the target values are current

  1. Confirm with your admin (or your integrated source system) that the Business Group and Business Product values you're trying to set are still current — not flagged obsolete or removed.
  2. If your organization integrates Hive9 with an external system that owns these picklists, changes there can take up to 24 hours to reach Hive9 because of attribute caching.
  3. If the value was recently removed from the source system and you still see it in Hive9's picklist, an admin can request a cache clear via contact Support.

Step 3 — Save the dependent attributes together

Because Business Product depends on Business Group, save them in this order:

  1. Select the new Business Group.
  2. Wait for the Business Product dropdown to refresh.
  3. Select the new Business Product.
  4. Save.

If you save Business Group alone, Business Product may revert or clear because the prior value is no longer valid under the new group.

[SCREENSHOT NEEDED — Dependent dropdown flow: Business Group → Business Product]

Step 4 — If saves still fail

Capture:

  • The tactic ID.
  • The exact values you're trying to set (Business Group : Business Product).
  • The error message or revert behavior you're seeing.

Contact Support with that information. We can confirm whether the picklist value is stale on the integration side or whether there's a dependency conflict to resolve.

Common questions

Why do I see old values in the dropdown after my admin removed them? Hive9 caches custom field data on a periodic refresh cycle (up to 24 hours for some integrations). Recently-removed values can linger in dropdowns until the cache refreshes.

Does changing Business Group affect other tactic attributes? Yes — any custom attribute that depends on Business Group will refresh. The most common dependent is Business Product, but your instance may have more.

Will my historical reporting break if I change these values? Reports show the value as of the tactic's current state. If you need a snapshot of the prior values, use Snapshots before making the change.

Related articles

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.