What's New in the Latest Build

This topic provides release notes for the very latest builds.  For information on different types of builds and a history of recent builds, see the Changes and Additions topic.

Build 176.1 introduces visibility scale limits (also known as scale ranges or zoom ranges) for layers in maps using the Layers pane.   The build also provides improvements in Esri Geodatabase (GDB), Shapefiles (SHP), DBF, and Google KML or KMZ dataports, facilitating interchange with Google products.


Visibility Scale Limits



The new capability makes it easy to create map displays that automatically show or hide layers depending on the zoom level (scale) of the map view.  We can automatically turn on more detailed layers as we zoom into a map, or show different content depending on the zoom level.


Dataports - Import / Export




Build 176 is a new base build, incorporating all improvements in the 9.0.175.x series of builds.   It is recommended for all users. Changes since include a 32-bit mode launch option for SQL for ArcGIS Pro, Refresh within ArcGIS Pro, mobile geodatabase support, and GPKG and SQLite layers within ArcGIS Pro support.  Also added for Advanced moved are new options to specify system colors, a new dataport for Google Sheets, and enhancements to the layers pane.


Additions and Changes



SQL for ArcGIS Pro




Build 175.7 concentrates on small adjustments, library updates, and fixes in preparation for wrapping up the current series of cutting edge builds and issuing a new base build.


Additions and Changes




Third Party Updates




Build 175.6 adds even more formatting options for field values, including the ability to launch URLs from table fields in browsers.  Styles also include the ability to set angular measurements, such as latitude and longitude values in degrees, in different formats.  A new style also allows choice fields in tables.  Styles set in tables are now automatically inherited by labels.   Language options have been extended to include over 600 languages, supporting the full set of languages in Windows 10.  


Build 175.6 also adds a new dataport for KoBoToolbox, a widely used open source technology for data acquisition using mobile clients or a web browser. The data can be hosted on a server provided by KoBoToolbox (there are generous free options), or on your own system with KoBoToolbox.  The new capability makes it easy to acquire data in the field using survey forms and to instantly make that data available within a Manifold project.


The next build is expected to fill missing pieces for features added during the 175.x build series, add various small items based on user feedback, fix outstanding bugs, and to go public as the next base build, 176.0.








A typical use might be StringFormatNumber([Latitude], 'adN2', '')  which would result in a numeric value of -6.0363 being formatted as the string 6.04º S.   See the Styling Table Fields topic and the StringFormatNumber entry in the String SQL Functions topic for many more examples.







Table Editing




Data Collection with KoBo





Build 175.5 is a large build with many new features.  It utilizes new formatting functions introduced in the prior build to provide point-and-click formatting of data displayed in tables with a very wide range of preset and custom formatting options for different data types.  Upcoming builds will automatically apply formatting specified in tables to labels and other settings.   


Build 175.5 also introduces new formatting functions,  new utility functions, and improvements in the Schema dialog.





Table Formatting








Formatting Functions










Other Query Functions







Build 175.4 begins adding formatting options for field values. This build adds query functions that format values of various types. Subsequent builds will allow applying this formatting to fields in tables and queries, and automatically carry it over to labels.  This build can be used immediately to format values in labels by using expressions in the label text pattern.







Query Functions and Format Patterns








Illustrations: Simple format changes allow creating many different labels and strings from a text field and a datetime field.







Illustrations: Specifying a language-country code automatically sets the format and language used. The exact same datetime value shown using D format with language set to English using en-US, German using de-DE, Cherokee using chr-US, and Indian Kashmiri using ks-IN shown above.





? StringFormatDurationDays(1.133, '', '') -- 97891 (seconds)

? StringFormatDurationDays(1.133, 'd:hh', '') -- 1:03

? StringFormatDurationDays(1.133, 'h:mm:ss', '') -- 27:11:31









Other Query Functions





SELECT [name], UuidMakeNew() AS [uuid] FROM [cities table];


The result of the above query is that all records ill have the same UUID. Because the query engine sees that the call to UuidMakeNew() is exactly the same for each record, it calls the function once, caches the result, and then copies the result into each record.



SELECT [name], UuidMakeNewRef([name]) AS [uuid] FROM [cities table];


In the above query, each record will have a new UUID generated. Because the calls to UuidMakeNewRef(...) are different between records, the query engine sees that and dutifully calls the function anew for each record.


The following allows creating a computed field with the current date, which will update itself after some of the fields are changed:



ALTER TABLE [cities table] (

  ADD [last_edited] DATETIME AS [[

    DateTimeCurrentRef([name] & [state] & CAST([population] AS NVARCHAR))




The query takes a table named cities table and adds a computed datetime field named last_edited. Adding a field populates it with the current date. If we then pick some record and change the value of one of the fields mentioned in the expression, such as name, state or population, the computed field in that record will be recomputed and set to the now-current date.

Build 175.3 reworks labels to use a text pattern instead of a text field.   The new system applies to all use of labels, such as storage, rendering, printing, and so on.  A text pattern is much more flexible than a text field: it can reference more than one field, and it also allows easy changes to label texts without changing the table (tables can be very big, or may not have permissions to be altered).   Future builds will allow formatting field values in the pattern, and will include various improvements for rendering labels.   Support for GDB is gradually being extended, and future builds will include several updates specific to SQL for ArcGIS.



Illustration above:  Labels can include expressions that use almost any SQL function and feature, such as CASE.   The Style pane makes it easy to edit existing label text.











New Video

Check out the new video providing a tutorial introduction to creating labels:


5 Minute Tutorial - Labels from Fields and Expressions - A quick look at the new label system in Manifold Release 9 that makes it easy to create labels from fields and expressions.   Create label text from multiple fields and also using expressions, taking advantage of any of the hundreds of SQL functions provided in Manifold.  A new addition to the Style pane for labels makes it really easy to edit label text, including a full expression builder.  Works in the free Manifold Viewer, too!



See Also

Changes and Additions