How to fix missing approval version on "update glossary term" workflow?

Hi Marc Sellers,

The Approval connector in Purview (and similar workflow systems) can have different versions or schemas. The backend uses the version field to ensure the action’s definition matches what it expects. You are right, this requirement of version isn’t explicitly documented in the Purview workflow connectors documentation. (Enrichment of the same will be requested.)

To get around this, you have a couple of options:

• Re-add or Reset the step:
  Delete the action and add it back into your workflow. Then immediately fill in the required parameters with static values for a test. Re-adding the Update glossary term should bring in any hidden defaults. After re-adding, try saving the workflow before inserting dynamic expressions. This may allow the system to auto-insert the correct version metadata.
  Microsoft Learn Link: Workflow Business Terms Approval
• Manually specify the version via code or API: Purview workflows can be managed via the REST API. If the UI continues not to save, you can fetch the workflow JSON (using the Workflow - Get API), add a "version": "1.0" field under the Start and wait for an approval action, and use Workflow - CreateOrReplace to update it. This directly ensures the JSON has the field. (This approach requires some development effort. Microsoft’s Purview REST documentation provides the JSON schema for workflows, where the approval action is of type "Approval", though it doesn’t list version – presumably the service can accept a version property.)

Microsoft learn link: Start and wait for an approval

If this answers your query, please click Accept Answer and Upvote for was this answer helpful.