(MID-40057) Spatial Manager was throwing rendering map error while previewing the MRR WMS
layer. When attempting to preview a raster image built in EPSG:3857 in the WMS layer setup, a
GetMap request failure error was displayed as: WMSEx_ErrorRenderingMap: Error rendering
map.
(MID-41628) The DBF TAB file was not uploading in the Map Uploader.
(MID-41973) In Search Nearest SOAP and Search Nearest REST, the values of
tablePointAttributeName and geomPointAttributeName were appearing interchanged in the
response.
(MID-42055) Spatial Manager was not displaying the resource (for example, a NamedTable)
that pointed to a NoSQL database source.
(MID-42058) Spatial Manager was not displaying the NamedTable that pointed to the Extensible
Data Provider.
(MID-42060) While creating a layer, under the Define Style Override display style, the image
displayed for the region fill styles was often visually clipped, particularly for more complex
patterns.
(MID-42092) Join with XY Table was not working.
(MID-42121) The Write Spatial stage was throwing an error for Delete By filter when the
filter uses variables.
(MID-42130) For Generic JDBC, the query made on a table was not working if the schema name
or the schema hierarchy contained a dot in the name.
(MID-42174) The Map Uploader was sending date and time thematic information in a format that
does not comply with ISO 8601. This is now the standard for Spectrum Spatial.
(MID-42280) When a label layer had an offset of zero, the map was failing to upload (using
the Map Uploader). Additionally, when a map already had a label layer with an offset set to
zero, it was failing to load in Spatial Manager 12.0 SP2.
(MID-42300) Extensible Data Providers were not working in Spectrum 12.0 SP1 and Spectrum
12.0 SP2 when referencing an external named connection.
(MID-42551) The classified Grid MRR files created using the MapInfo Pro Advanced from
version 16.0.3 and forward tools, with compression, were not displaying.
(MID-42552) Spatial Manager was not displaying the NamedLabelSource correctly. Any
NamedLabelSource without an offset element was causing errors in Spatial Manager when accessing
its detail page or the label layer that used it. Any label offset of zero is saved without this
element. See related issue MID-42280.
(MID-42663) Some dataflow options not relevant to the Spatial Calculator were resulting in
an exception.