# Recommended approach for automatically creating UDT instances when registering equipment in Perspective?

**URL:** <https://forum.inductiveautomation.com/t/recommended-approach-for-automatically-creating-udt-instances-when-registering-equipment-in-perspective/117753>\
**Category:** Ignition\
**Tags:** ignition83, perspective\
**Created:** [November 5, 2026, 4:20am UTC](https://forum.inductiveautomation.com/t/recommended-approach-for-automatically-creating-udt-instances-when-registering-equipment-in-perspective/117753 "2026-11-05T04:20:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sylee](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@sylee](https://forum.inductiveautomation.com/u/sylee)\
**Post date:** [November 5, 2026, 4:20am UTC](https://forum.inductiveautomation.com/t/recommended-approach-for-automatically-creating-udt-instances-when-registering-equipment-in-perspective/117753/1 "2026-11-05T04:20:23Z")

</div>

Hi everyone,

I’m working on a DCIM project in Ignition 8.3.1 Perspective.

Users can register Busways through a management screen. Currently, the Save button calls a project script that inserts or updates the equipment information in a database using Named Queries.

I would also like to automatically create a UDT instance when a Busway is registered, and update its parameters when the equipment settings change. Users would select an existing Ignition device connection from a dropdown, and that device name would be passed to the UDT as a parameter.

I’m considering calling `system.tag.configure()` in the same project script after the database save succeeds, using the database primary key as the instance name.

Is this a reasonable approach, or is there a better pattern for managing database records and dynamically created UDT instances?

In particular, how would you handle a case where the database save succeeds but tag creation fails? I’d appreciate any advice on keeping the database configuration and tag instances synchronized.

Thanks!