Any exports of more than 10,000 records (e.g.: 12,545 records found via a query in SSA) are, when then exported to .csv and viewed in Excel, are always shown truncated at 10,000 records. Record 10,001 to 12,545 would not be shown.
This is a major problem and seriously undermines an essential and core function of SSA.
Successive csv exports from SSA show the previous export in Excel
Let's say you wanted to run three polygon led LLPG point grabs in succession. You would do (and expect to see) this:
But what happens in v12.2.1 is….
Basically, successive exports are always one behind what you actually expect to see, even though the correct exported file is being viewed.
The only way to get around this is to not open directly from the web browser's download item but instead open Excel separately and select File> Open to the download item.
This appears to be a bug in SSA 12.2.1. It always worked correctly before.
NamedMaps falling out of map configs
At random times, in random map configs, random NamedMaps are falling out of map configs. The map config opens but without one or several NamedMaps, which are listed in a service error in top of SSA screen.
This is something that started to happen in either SSA12.2 or 12.2.1. It's a major service continuity problem.
The only solution is to recreate and re-upload the NamedMaps via a new workspace with a different name, remove the offending NamedMap and add in the new one into all effected map configs.
This issue has been discussed with Pitney Bowes support and other PB people. The issue has been acknowledged and I understand that a fix for it is in the SSA November 2018 release. Please confirm.
NamedMaps failing when structure of source tab file is changed
When upgrading from Stratus Connect to SSA one of the benefits was how it was possible to change the structure of a tab file uploaded to SSA as part of NamedMap and still have that NamedMap work in SSA. For example, I could add a field in the tab file or delete a field or rename a field without affecting the view-ability of that layer in the SSA NamedMaps. Whereas in Stratus Connect if the structure of a linked tab file was changed (e.g.: adding a field) the layer would stop work, and corrupt the group it was in. SSA got around that problem and was such a benefit to administrators.
However in SSA 12.2 and 12.2.1 this functionality has disappeared. Any changes made to a tab file which is part of a NamedMap will result in that NamedMap no longer working. This represents a step backwards and major problems for administrators and users alike. I'd like to see this bug fixed, please.
Thanks for that, Duri.
It's a complex issue and one that PB has already spent much time investigating on site and via Go To Meetings. I recall volatile being looked at, but I'll certainly mention it again the next time PB are looking into it.
PB seem to think it's about permissions to tables not staying in place. To ne honest I'm leaving this with PB to resolve. It only started happening in 12.2 and 12.2.1. Up until then it wasn't an issue. Although it may be coincidence, of course.