Hi,
I get this error when saving data into a particular WP#Workflow S#Scenario T#Time member.
Cannot execute step because the specified step classification doesn't exist for the workflow profile ...
The problem seems to be a disconnect between the account used in the Cube View having a different Workflow Channel as that defined in the Workflow Profile.
WP was set to Standard, the A# to NoDataLock. I've set both to Standard and it removes the error. I'll know add the appropriate Phase in the Workflow Channel and updated the WP and A#
We are seeing an interesting error while completing the "Load cube" step on an import step. I have asked around and no one has seen this specific error before, so I was hoping to get some clarification on what it means and how it should be addressed. We are on version 7.1.3.
For some background, we are in the early build stages of implementation. I am loading historical data through our designated Historical Data workflow. This input channel is set to "Load Unrelated Entities" and the channel is set to "AllChannelInput". We know we will be utilizing channels, so we want to make sure this import step can load once those channels are built out.
We were able to load to this workflow with no problems until we started assigning entities to the workflows that will be used after go-live. Once we assigned entities to the other workflows we received the below error:
Once we received the error, I tried multiple steps to troubleshoot:
1. Updated the channel on both the site workflow and the historical data workflow to be "Standard"
2. Updated the default workflow to have 2 import steps, one set up with "Standard" channel and one set up with "AllChannelInput" channel
3. Updated both of the parent base input workflows to have the "Workspace" instead of having one as "Confirm, Certify"
None of the above worked. The only solution that has worked has been setting at least one import step under each workflow to have a channel of "AllChannelInput". This is not a viable solution as we don't want the channels underneath a site workflow to have AllChannelInput. This is also not expected behavior of how workflows and channels have worked in the past.
Has anyone seen this error and/or can help us understand it better? Thank you!
Hi Jack - That solution may work for Guy; however, we don't want our accounts to be on the "Standard" channel. We are splitting our channels out by UD not by account, so we need all accounts available for all channels. Standard would limit that. Similar to what I mentioned in my post about updating our WF channels, Guy's solution works but isn't expected behavior. ManasviR tagging if you have anything to add.
Hey Claire; after some internal discussions with architects, I've opened a ticket for you. Someone will get in touch. If you could come back to report the solution once they find it, that would be fab.
