I'm about to make a little release today but will try and fix this for the next release after this if you can help me figure out a good solution that won't break in other situations like upgrades where dbo was already used during object creation.
It might work if all the scripts where changed to not use any prefix at all. Can you help me with testing on a local machine? If you have time it would be much appreciated and would help get a solution for this.
What I'd like you to do is test this theory with a clean install using scripts with all owner prefixes removed starting with script Setup/applications/mojoportal-core/SchemaInstallScripts/mssql/2.3.4.config
and then the scripts newer than that in the SchemaUpgradeScripts/mssql folder
So you'd have to remove the prefixes using find and replace and maybe review visually some to make sure.
If that works then send me the modified scripts and I will test if it also works when upgrading installations that used dbo before. If so then we will replace with these new scripts and going forward always leave out owner prefix and this won't be a problem anymore and won't need any complicated instructions for this situation.
I think it should work but we need to make sure with testing.