I was able to find a way around after several weeks of trial and error and this was the solution I came up with. Install the supplied patch, after which edit the Nodelocal.js file in the Syracuse bin directory using the supplied codes as presented in the manual. But it must be noted that when editing the code you must ensure all opened tags are closed and the code is well indented if not you might disrupt the system to perform well so its advisable to have a copy of the initial set of codes in the Nodelocal.js file saved separately some where in case things goes wrong and ensure you restart the Sage Apache Services after this and with that I think you should be good to go. Don't change the code except where you need to supply you server name. Hope this helps. 

I was able to find a way around after several weeks of trial and error and this was the solution I came up with. Install the supplied patch, after which edit the Nodelocal.js file in the Syracuse bin directory using the supplied codes as presented in the manual. But it must be noted that when editing the code you must ensure all opened tags are closed and the code is well indented if not you might disrupt the system to perform well so its advisable to have a copy of the initial set of codes in the Nodelocal.js file saved separately some where in case things goes wrong and ensure you restart the Sage Apache Services after this and with that I think you should be good to go. Don't change the code except where you need to supply you server name. Hope this helps. 

What "supplied patch" are you referring to?  

You have it in the Template Installation folder it's a DAT file starting with path_ZBITG_*********

As we are experincing this issue as well, and this solution does not appear sustainable, does anyone have news as to whether this issue will be going away as supported by Sage directly? Will this be fixed in an upcoming patch or something?

We were informed that this is a browser security issue, so should we be using a specified browser that does work?

We literally cannot embed any SEI reports into Landing Pages, despite that being one of the main reasons we upgraded to V12.

Hello Christianson,

Have you read the SEI online help here onlinehelp.sageenterpriseintelligence.com/.../SageX3-embed.htm

Thank you for this reference. I have passed it along to my team and we are exploring it for our uses.