Managing Mappings
After you scan a DatasourceA connection from Informer to a database or other system of record, such as PostgreSQL, SQL Server, or UniVerse., its Mappings are yours to curate: scan in the tables and fields you need, hide the ones you don't, group and restrict them, link related ones so queries can span them, and add custom-expression Fields the database does not expose on its own.
In this section
| Article | In one line |
|---|---|
| Scanning a Datasource | Bring Mappings and Fields into Informer, and rescan to stay in sync. |
| Hiding and unhiding Mappings | Keep irrelevant tables out of users' way. |
| Mapping Sets and restricted Fields | Group Mappings and restrict Fields for access control. |
| Custom Field Expressions | Add Fields computed by a native database expression. |
| Linking Mappings | Relate Mappings so a Query can pull Fields across them. |
| Mapping Suites | Group period-partitioned Mappings behind one logical Mapping. |
| Datasource Field options | Configure how individual Fields behave. |