Cross-Module Association to the System module must have the Owner property set to Default Workaround?

My Project is attempting an upgrade from Version 6 to Version 7.  While working through the Deprecation errors I ran into an issue where I am required to update a cross-module association involving a relationship where the System.Session is the Child. When I do update that association to select owner by default (instead of both) I get several errors that require me to make several edits to multiple microflows. Is there anyway I can upgrade to version 7 without having to make the Sysytem.Session Module the default owner of a cross-module association?      
1 answers

No because in Mendix 7 there is a fundamental change how session objects are stored and communicated between server and client. I think you have to refactor that part of your application.