Forum Discussion
Microsoft Office Implicit Intersection Operator "@" impacting TM1 "DBRW" Database Write Back Formula
So how will TM1/IBM Planning Analytics DBRW formula work to write back to the database?
Are there no other organization facing similar issue? How do they work around this? Any interim solution?
Putra_Bala Did you ever find an answer to this? Did you open a case with IBM?
- Putra_BalaJun 12, 2020Copper Contributor
Hi JimGeraci ,
Yes, I got this resolved. Apparently you can do a find "@" and replace with "" on the impacted Excel report sheet/workbook. This was the solution provided by IBM.
I did open a case with Microsoft as well and did have some discussions with them about this.
They informed that they have switched-off the implicit Intersection Operator from being default in the future releases of Microsoft updates(Version 2003 - End of March 2020 onward).
Regards,
PB
- JimGeraciJun 12, 2020Copper Contributor
Putra_Bala of course IBM would tell you to find and replace *smh*
Good to hear microsoft will turn it off by default. Thanks for the update 🙂
- PeterBartholomew1Jul 01, 2020Silver Contributor
I am not sure I understand why MS should turn off the "@" operator by default. Their main focus should be to ensure that the new versions of Excel run old files and obtain the same results (backward compatibility). If third party code reads or writes formulas, as opposed to values, then there is no promise that the development will not break the functionality (unless it uses a formally specified API). It is up to the third party developer to rework their application.