Workflow Activation fails during solution import - Column name stageid in table WorkflowBase

(0) Share

Report

Posted on by Helpful

382

I have two managed solutions:

Entities & Apps
Flows

In the last couple of weeks I am receiving reproducible warnings while importing a manged solution with modern workflows resulting in no activation on import. The flow(s) can be activated manually after import.

This occurs with one flow regularly, occasionally with another flow. These flows have not changed for months and have been importing without issue for that duration.

Import Log Values:

ItemType: Workflow Activation
ErrorCode: 0x80040216
ErrorText: Microsoft.Crm.CrmException: An attribute with the specified name already exists. Exception Message: Column names in each table must be unique. Column name 'stageid' in table 'WorkflowBase' is specified more than once.

This is reproducible in any CDS environment type: TRIAL, STAGING or PRODUCTION. Most recently observed in CDS database version: 9.1.0.14143

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

mjburley 370 on at

Like (0)

Report
Copy link

Link copied!

I spun up a brand new CDS instance, and imported an unmanaged solution with a canvas app and flows.

On trying to turn on the flows I get the same message. Have not tried managed yet ...

Your flow could not turn on: MyFlowName. Error: Microsoft.Crm.CrmException: An attribute with the specified name already exists. Exception Message: Column names in each table must be unique. Column name 'stageid' in table 'WorkflowBase' is specified more than once.
Any progress on this?

Was this reply helpful? Yes No
Helpful 382 on at

Like (0)

Report
Copy link

Link copied!

I believe it’s currently being investigated.
I also tested in a new environment with 2020 wave 1 released turned ON and did not see the issue.

Was this reply helpful? Yes No
namurdock 17 on at

Like (0)

Report
Copy link

Link copied!

I just had the same thing, it ended up being that the environment was in Admin mode still after a deployment. Worth a check.

Was this reply helpful? Yes No