Free cookie consent management tool by TermsFeed

a!map() Function

Function

a!map( key1, keyN )

Creates a map of values (Any Type) with each value stored at the corresponding string key. Values stored in maps are not wrapped in variants.

See also: Appian Data Types

Parameters

Keyword Type Description

key1

Any Type

A key value pair to store in the map. The value is not wrapped in a variant.

keyN

Any Type

Any additional key value pairs, as needed.

Returns

Map

Usage consideration

Function requirements

  • Keywords must be unique.
  • Keywords are not case sensitive.

Maps vs. dictionaries

While similar to a dictionary, which uses curly braces {}, the values stored in a map are not wrapped in variants. This makes it much easier to get values back out of maps by indexing, without having to worry about type casting. There are no advantages to using dictionaries; prefer using maps over dictionaries where possible.

Casting a map

  • A map can be cast to a dictionary, CDT, record, or text.
  • A dictionary, CDT, or record can be cast to a map.

Examples

Single map

1

a!map(id: 1, name: "Jane Doe")

List of maps

1
2
3
4

{
   a!map(id: 1, name: "Jane Doe"),
   a!map(id: 2, name: "John Doe")
}

Feature compatibility

The table below lists this function's compatibility with various features in Appian.
Feature Compatibility Note
Portals Compatible
Offline Mobile Compatible
Sync-Time Custom Record Fields Compatible

Can be used to create a custom record field that only evaluates at sync time.
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.
Process Reports Incompatible

Cannot be used to configure a process report.
Process Events Incompatible

Cannot be used to configure a process event node, such as a start event or timer event.
Process Autoscaling Compatible

Feedback