So this is not a critical bug, but it is very annoying, in the 25/9 release the bug was even worse as no volume were displayed at all, this was corrected but not entirely.
We need to have it as Results Level, since it must be univocally identified from the rest of folders. We are refactoring this part so we don’t need to force this, but for now it is our bug
The main problem is that there could be more than one Results folder and that would crash the workflow.
You don’t need to use Level. You can use attribute instead. Like shn.SetItemAttribute(resultsItem, 'Results', 1)
then shn.HasItemAttribute(resultsItem, 'Results')
will return True
It works on all kinds of items. Yes it needs to be string. Check the error log if anything strange happens. Usually it should tell you what went wrong and why.
And I found the cause of the original problem: it is a refresh issue, the scene needs to be refreshed, but currently I have tried the StartModify - EndModify things and they don’t refresh the scene.
Basically I create the scene, no items visible
save the scene to a mrb file, close current scene and load back the mrb and voila, the items magically appear.
How exactly do you use StartModify / EndModify? We usually use it on individual nodes, in which case it should be OK, because on EndModify the one corresponding SH item updates itself and that’s it.
I recently integrated a change that allows subject hierarchy to be stable with BatchProcessing, maybe you should use that instead.