Table and field mapping for assets
Asset mappings are a Jira Table Mapping with Jira Entity Type set to Asset, so the general concepts in Table and field mapping apply here as well. This page covers what is specific to synchronizing assets.
Supported source tables
| BC Source Table | Asset Object Type |
|---|---|
| Customer | Customer |
| Contact (Person type only) | Customer Employee |
| Project | Project |
| Service Asset | Service Asset |
These are the object types created by the default schema; a mapping can also target a custom object type modeled as described in Asset schema.
Unlike Organization and Customer mappings, more than one enabled asset mapping is allowed for the same source table, as long as each targets a different asset object type - the table filter below decides which records go to which mapping.
Creating an asset table mapping
On a new Jira Table Mapping, set Jira Entity Type to Asset. The Asset Configuration section that appears is used to choose the Asset Schema Code and Asset Object Type Code to synchronize to - both must already be Synced. Select the assets OAuth2 Setup Code (setup) as the connection, the same as for any other mapping.
Field mapping
For the Asset entity type, the Field Mappings part targets a schema attribute instead of a free-form Jira field ID:
| Field | Meaning |
|---|---|
| Target Attribute | The Synced attribute of the mapping's object type to write to |
| Source Type | Field (the value comes from a Business Central field) or Constant (a fixed value) |
| Source Field No. | The Business Central field to synchronize, when Source Type is Field |
| Constant Value | The fixed value to synchronize, when Source Type is Constant |
| Transformation Rule | An optional transformation rule applied to the source value |
An Object Reference attribute can only be targeted with Source Type Field, using a source field that has a table relation.
Table filter
Each asset mapping can be restricted to a subset of records with a table filter:
- On the table mapping card, in the Asset Configuration section, select the Table Filter field.
- Use the standard filter dialog to define which records the mapping applies to.
- Confirm the filter.
A record is only synchronized as an asset if it matches the table filter of at least one enabled asset mapping for its source table. An empty filter matches every record.
Enabling synchronization
- For Customer and Contact, asset synchronization is enabled the same way as Organization and Customer synchronization - see Enabling and disabling synchronization and Mass-enabling synchronization for existing records in Table and field mapping. The same Enable Jira Sync field drives both the Organization/Customer synchronization and the asset synchronization for the same record.
- For Project, turning on Enable Jira Sync on the Project card starts synchronization for that project.
- For Service Asset, there is no separate enable step - every Service Asset that matches an enabled mapping's table filter is synchronized automatically as soon as it is created.
Automatic activation
Activation Rules can also be used on Customer and Contact mappings targeting the Asset entity type, using the same rule types described there. For Project and Service Asset mappings, the table filter above already determines which records are synchronized, so activation rules are not used.