Is this something which has to be considered in sioc support also? As a workaround it can be fixed with own sioc code, I guess.