moving-report-xml-manually.md
... ...
@@ -10,4 +10,4 @@ There are many possible causes of this:
10 10
11 11
2) A malformed ReportSet can also cause this issue. If you copied reports records in your DB, for example, with just ``ctrl-c`` & ``ctrl-v``. As a result, symbols such as ``\r\n`` can be lost. As a result, the whole XML data of the ReportSet becomes a single long string. When this happens, that ReportSet then becomes erroneous from the point of view of Izenda.AdHoc, and won't load/show in ReportList.
12 12
13
-3) Make sure TenantId values in ReportSet match the session values in the new deployment. When you copy ReportSet - without ``"_global_"`` tenant - report may be invisible to usual users.
... ...
\ No newline at end of file
0
+3) Make sure TenantId values in ReportSet match the session values in the new deployment. When you copy ReportSet - without ``"_global_"`` tenant - some or all reports may be invisible to usual users.
... ...
\ No newline at end of file