Introduction

You can use the Import Tool to trigger actions while importing the Excel file. You just need to indicate the action name.

it cannot invoke an action with arguments


You also have specific and useful actions available:

  • "{remove}" will remove the component. It is really helpful because excel tool will generally just set or reset components not delete some.
  • "{updateTemplate}" will update the component if it’s associated to a valid .ntpl file (Niagara template)

Example


Internal idBaseTemplateNameAction
Id to reuse the component. Use#Reference where the component will be createdTemplate name with subpathName of the instance to create





#ModbusAsyncNetwork$Drivers
ModbusAsyncNetwork
{remove}

Will remove the ModbusAsyncNetwork

Try it yourself !

Here is the file used in the above import example. Download it, try importing it and see the result. (Delete the remove action first to import the component, add the action and import again)

triggerAction.xlsx

You can also use a subColumn to trigger actions on a subComponent, an alarm extension or a history extension

Example

subcomponent:MySubComponentType

nameinfo:{mySFormat}slot:pathToMySlotaction

You CANNOT use the updateTemplate command in a subComponent

Accepted values

  • Actions invokable by the component in the row (you can set several actions to invoke with a semicolon separated list. Ex. : auto;emergencyAuto)

  • {remove}

  • {updateTemplate}


Be careful with this option because the result (the execution of many actions during the import) can consume a lot of resources and, depending on what you're trying to do, can lead to an Engine Watchdog.