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.
A bit of a shot in the dark from me, but please can you test that : Go to your Administration > Workflow profile and change the workflow name and save. Then put it back the way it was and save. Can you tell us what is your Workflow Name? A step could be a task within a workflow name but there are no official definition of a step - or not that I am aware of 🙂
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 tried that too as well to no success. One is set to "Import, Validate, Process" and the other is "Import, Validate, Load" and it didn't work when both were set to "Import, Validate, and Load" either.
I agree with cdever: this is not expected behavior, nor how WFs Channels use to work before 7.1. I am facing the same issue and GuyRogers workaround is only valid when Channels are not part of the solution.
JackLacava, do you mind updating us on the status of the ticket you created?
Thanks, JackLacava for the answer. Could you please share the ticket number you created to reference it with OS Support to help them out not start from scratch with the new ticket I will be creating?
cdever, could you please provide a quick update on your issue, as it is exactly the same I am facing in 7.1?
We are seeing a similar error and behavior on a client that is on version 7.0.1. We are trying to clear data with a data management job that is doing AllEntities.base. We get the first error saying that we need a step classification. Then we get the second error saying saying we need an active profile for workflow channels for Forms. I do not think it is correct behavior when all of the channels are active on the workflow. We had to unassign the entity and then put allchannelinput on the default forms to delete the data. Is there any resolution to this behavior?
Hi awest, Unfortunately, there does not seem to be a fix to this behavior (which is the same we reported to OS but on the Forms Channel in your case). The only workaround I've found is to remove the Entities. cdever ssuggests that this may have been fixed in 7.2.2, although OneStream has not acknowledged the defect to the best of my knowledge. The defect seems to be checking a completely different and even invalid/unexisting Data Unit. For example, even if I load historical data to Actuals (Scenario Type Actual), I would get the error pointing to WP#EntityA:S#Actual_TB (Scenario Type Administration, which is a WF not even available to Scenario Type Actual!). I'll update this thread after am upgrade to 7.2.2. Regards, Mauro.
Update: this behavior can be replicated even in version 8. I believe changing certain WF settings after the WF has been used forces a corruption in OS tracking of WF statuses/settings. It seems that we have to be ready to reset a scenario/year to implement/modify channels after the fact.
