Skip to main content

​
Overview

Trx Attribute Entity Relational Import Update lets you update existing entity records in NeuronCx — including the relationships between them. For example, you can link a branch to its branch type, or assign a map location to a centre, all from a single sheet run. This import handles two things at once — regular attribute value updates and relationship updates — so you don’t need separate imports for each.
This import updates existing records only. Every row in your sheet must have a primary ID — rows without one are skipped automatically, without an error.

​
Prerequisites

  • Your Google Sheet must be shared with edit access so NeuronCx can read from it.
  • Every row must include the primary ID of the record you want to update. Rows without an ID are silently skipped.
  • The attribute definitions and relationships you’re updating must already exist in NeuronCx. This import never creates new attribute definitions or relationship types.
  • Columns without a header are skipped automatically.

​
Preparing Your Sheet

Your sheet must include the primary ID column. Beyond that, include one column per attribute or relationship you want to update.

​
Standard columns

​
Relation columns

Relation columns follow a specific naming format: For example: Relation_BranchType_319
  • <anyIdentifier> is a label that describes the relationship — for example BranchType.
  • <RelationId> is the ID of the permitted dependency — your administrator can confirm the correct value.
  • The cell value is the ID (or IDs) of the related entity to link. To link multiple entities in one cell, separate the IDs with a comma — for example 1138,1137,1136,1135.
The relation column name must follow this pattern exactly — two underscores, no spaces, and it must start with Relation. For example: Relation_BranchType_319. An incorrect column name will be ignored.
Screenshot 2026 08 29 124015
You can include multiple relation columns in the same sheet — one column per relationship type you want to update. Each is processed independently.
To link a record to multiple related entities at once, enter their IDs as a comma-separated list in the relation column cell — for example 1138,1137,1136,1135.

​
Running the Import

​
Setting up a new import

1

Open Imports

Navigate to Home > Ontology > Attribute Settings & Bulk Edit, then click the Imports tab.
2

Click + Import

Click the + Import button in the top right to open the New Import modal.
Import Button 8
3

Give it a label

Enter a name that describes this import — for example, “Branch Relational Update.”Label 7
4

Add the Google Sheet ID

Paste the sheet ID or the full Google Sheets URL — NeuronCx will extract the ID automatically.
Sheet Id 2
5

Verify

Click Verify. NeuronCx confirms it can read the sheet and shows you the row and column count — use this to catch an empty or wrong sheet before continuing.Verify 9
6

Select the import type

In the Import type panel on the left, select Entities & Attributes. Then choose Trx Attribute Entity Relational Import Update (#13) from the list on the right.
Import Type 3
7

Create the import

Click Create import. The import now appears in your list under Entities & Attributes, ready to run.Create Import

​
Running the import

1

Find the import

From the Data Import list, locate the import you just created. You can filter by Entities & Attributes to narrow the list.
2

Open the import

Click the arrow icon on the import row to open it.
3

Select the Transaction Attribute

Choose the attribute entity you want to update from the Select Transaction Attribute dropdown.Selecting Transactional Attribute
4

Click Trigger

Click the green Trigger button to run the import.

​
Checking the Result

Once the run completes, the Trigger Log at the bottom of the screen shows each run with the workflow used, the number of rows processed, and when it ran.
Triggre Log
If a row shows as skipped, check that its primary ID column is filled in and matches a record that already exists in NeuronCx.

​
Limits to Keep in Mind

  • This import updates existing records only. To create new entity records, use Trx Attribute Entity Import (Type 11) instead.
  • Every row must have a primary ID. Rows without one are skipped silently — they won’t appear as errors in the run log.
  • Relation column names must follow the Relation_<identifier>_<RelationId> format exactly — no spaces, two underscores, starting with Relation. Columns that don’t match this pattern are ignored.
  • Multiple related entity IDs can be set in a single relation column by separating them with commas.
  • Columns without a header are skipped automatically.
  • Only one import runs at a time. If another import is already running, this one will queue and wait its turn.