Team Dynamix

IT Service Management

Overview

[!NOTE]

The TeamDynamix connector integrates with the TeamDynamix IT Service Management (ITSM) and IT Asset Management (ITAM) platform through its Web API. It synchronizes service-desk and asset inventory data into Brinqa, including tickets, people, groups, locations, assets, configuration items, and accounts/departments. The connector also supports creating and updating tickets back in TeamDynamix.

All data is retrieved from a TeamDynamix Web API instance (for example, https://tdx.<domain>.com/TDWebApi/). Asset and Configuration Item data is collected across every application of type Asset/CI exposed by the instance.

Data retrieved from TeamDynamix

Connector Object	Required	Maps to Data Model
Ticket	Yes	Ticket
People	Yes	Person
Group	Yes	Team
Location	Yes	Location
Asset	Yes	Host
Configuration Item	Yes	Configuration Item
Account	Yes	Account

Model relationships

note

For detailed steps on how to view the data retrieved from TeamDynamix in the Brinqa Platform, see How to view your data.

note

The Ticket object is not retrieved or mapped by default. To retrieve tickets from your TeamDynamix environment, configure the corresponding setting and create your own mapping; contact your Brinqa support team for guidance.

Setup

Connection settings

When setting up a data integration, select TeamDynamix from the Connector dropdown and provide the following:

Setting	Required	Default	Description
API URL	No	—	TeamDynamix API URL
Username	No	—	TeamDynamix username
Password	No	—	TeamDynamix user password
Application ID	No	—	Ticket Application ID
Page size	No	—	Maximum number of hosts to request per API request
Parallel requests	No	—	Maximum number of parallel API requests
Maximum retries	No	—	The maximum number of retry attempts before giving up a request

Authentication

The connector authenticates with the TeamDynamix Web API using administrative-account credentials (username and password). It calls the authentication endpoint once, receives a JWT bearer token, and reuses that token as a Bearer Authorization header on every subsequent API request until it expires, at which point a new token is requested automatically.

Authentication Endpoint

Method	URL
POST	api/auth

Request Headers

Header	Value
Content-Type	application/x-www-form-urlencoded

Request Body

The credentials are sent as URL-encoded form parameters:

username=<configured username>&password=<configured password>

Sample Response

The endpoint returns the raw JWT token as a plain string (not a JSON object):

eyJhbGciOiJSUzI1NiIsImtpZCI6Ik...<truncated JWT>...sQXz9w

Response Fields

Field	Description
(response body)	The bare JWT access token used for subsequent requests.

Using the Token

For every data request, the token is sent in the Authorization header:

Header	Value
Authorization	Bearer <jwt token>
Content-Type	application/json

---

How to obtain TeamDynamix credentials

Obtain the required credentials (URL, Username, Password) from your TeamDynamix administrator or the TeamDynamix admin console, then enter them in the connection settings above.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Ticket

Source Field Name	SDM Attribute
Ticket.AccountID	ACCOUNT_ID
Ticket.AccountName	ACCOUNT_NAME
Ticket.ActualMinutes	ACTUAL_MINUTES
Ticket.AppID	APP_ID
Ticket.ArticleAppID	ARTICLE_APP_ID
Ticket.ArticleCategoryPathNames	ARTICLE_CATEGORY_PATH_NAMES
Ticket.ArticleID	ARTICLE_ID
Ticket.ArticleShortcutID	ARTICLE_SHORTCUT_ID
Ticket.ArticleStatus	ARTICLE_STATUS
Ticket.ArticleSubject	ARTICLE_SUBJECT
Ticket.Attributes[].Value	CUSTOM_<id>
Ticket.Classification	CLASSIFICATION
Ticket.ClassificationName	CLASSIFICATION_NAME
Ticket.CompletedDate	COMPLETED_DATE
Ticket.CompletedFullName	COMPLETED_FULL_NAME
Ticket.CompletedUid	COMPLETED_UID
Ticket.ConvertedToTaskDate	CONVERTED_TO_TASK_DATE
Ticket.ConvertedToTaskFullName	CONVERTED_TO_TASK_FULL_NAME
Ticket.ConvertedToTaskUid	CONVERTED_TO_TASK_UID
Ticket.CreatedDate	SOURCE_CREATED_DATE
Ticket.CreatedEmail	CREATED_CREATED_EMAIL
Ticket.CreatedFullName	CREATED_FULL_NAME
Ticket.CreatedUid	CREATED_UID
Ticket.DaysOld	DAYS_OLD
Ticket.Description	DESCRIPTION
Ticket.EndDate	END_DATE
Ticket.EstimatedMinutes	ESTIMATED_MINUTES
Ticket.ExpensesBudget	EXPENSES_BUDGET
Ticket.ExpensesBudgetUsed	EXPENSES_BUDGET_USED
Ticket.FormID	FORM_ID
Ticket.FormName	FORM_NAME
Ticket.GoesOffHoldDate	GOES_OFF_HOLD_DATE
Ticket.ID	UID
Ticket.ImpactID	IMPACT_ID
Ticket.ImpactName	IMPACT_NAME
Ticket.IsConvertedToTask	IS_CONVERTED_TO_TASK
Ticket.IsOnHold	IS_ON_HOLD
Ticket.IsRichHtml	IS_RICH_HTML
Ticket.IsSlaResolveByViolated	IS_SLA_RESOLVE_BY_VIOLATED
Ticket.IsSlaRespondByViolated	IS_SLA_RESPOND_BY_VIOLATED
Ticket.IsSlaViolated	IS_SLA_VIOLATED
Ticket.LocationID	LOCATION_ID
Ticket.LocationName	LOCATION
Ticket.LocationRoomID	LOCATION_ROOM_ID
Ticket.LocationRoomName	LOCATION_ROOM_NAME
Ticket.ModifiedDate	SOURCE_LAST_MODIFIED
Ticket.ModifiedFullName	MODIFIED_FULL_NAME
Ticket.ModifiedUid	MODIFIED_UID
Ticket.Notify	NOTIFY
Ticket.ParentClass	PARENT_CLASS
Ticket.ParentID	PARENT_ID
Ticket.ParentTitle	PARENT_TITLE
Ticket.PlacedOnHoldDate	PLACED_ON_HOLD_DATE
Ticket.PriorityID	PRIORITY_ID
Ticket.PriorityName	PRIORITY_NAME
Ticket.PriorityOrder	PRIORITY_ORDER
Ticket.RefCode	REF_CODE
Ticket.RequestorEmail	REQUESTOR_EMAIL
Ticket.RequestorFirstName	REQUESTOR_FIRST_NAME
Ticket.RequestorLastName	REQUESTOR_LAST_NAME
Ticket.RequestorName	REQUESTOR_NAME
Ticket.RequestorPhone	REQUESTOR_PHONE
Ticket.RequestorUid	REQUESTOR_UID
Ticket.ResolveByDate	RESOLVE_BY_DATE
Ticket.RespondByDate	RESPOND_BY_DATE
Ticket.RespondedDate	RESPONDED_DATE
Ticket.RespondedFullName	RESPONDED_FULL_NAME
Ticket.RespondedUid	RESPONDED_UID
Ticket.ResponsibleEmail	RESPONSIBLE_EMAIL
Ticket.ResponsibleFullName	RESPONSIBLE_FULL_NAME
Ticket.ResponsibleGroupID	RESPONSIBLE_GROUP_ID
Ticket.ResponsibleGroupName	RESPONSIBLE_GROUP_NAME
Ticket.ResponsibleUid	RESPONSIBLE_UID
Ticket.ReviewerEmail	REVIEWER_EMAIL
Ticket.ReviewerFullName	REVIEWER_FULL_NAME
Ticket.ReviewerUid	REVIEWER_UID
Ticket.ReviewingGroupID	REVIEWING_GROUP_ID
Ticket.ReviewingGroupName	REVIEWING_GROUP_NAME
Ticket.ServiceCategoryID	SERVICE_CATEGORY_ID
Ticket.ServiceCategoryName	SERVICE_CATEGORY_NAME
Ticket.ServiceID	SERVICE_ID
Ticket.ServiceName	SERVICE_NAME
Ticket.ServiceOfferingID	SERVICE_OFFERING_ID
Ticket.ServiceOfferingName	SERVICE_OFFERING_NAME
Ticket.SlaBeginDate	SLA_BEGIN_DATE
Ticket.SlaID	SLA_ID
Ticket.SlaName	SLA_NAME
Ticket.SourceID	SOURCE_ID
Ticket.SourceName	SOURCE_NAME
Ticket.StartDate	START_DATE
Ticket.StatusClass	STATUS_CLASS
Ticket.StatusID	STATUS_ID
Ticket.StatusName	STATUS
Ticket.TaskID	TASK_ID
Ticket.TaskPercentComplete	TASK_PERCENT_COMPLETE
Ticket.TaskPlanID	TASK_PLAN_ID
Ticket.TaskPlanName	TASK_PLAN_NAME
Ticket.TaskProjectID	TASK_PROJECT_ID
Ticket.TaskProjectName	TASK_PROJECT_NAME
Ticket.TaskTitle	TASK_TITLE
Ticket.TimeBudget	TIME_BUDGET
Ticket.TimeBudgetUsed	TIME_BUDGET_USED
Ticket.Title	TITLE
Ticket.TypeCategoryID	TYPE_CATEGORY_ID
Ticket.TypeCategoryName	TYPE_CATEGORY_NAME
Ticket.TypeID	TYPE_ID
Ticket.TypeName	TYPE_NAME
Ticket.UrgencyID	URGENCY_ID
Ticket.UrgencyName	URGENCY_NAME
Ticket.Uri	URL
Ticket.WorkflowConfigurationID	WORKFLOW_CONFIGURATION_ID
Ticket.WorkflowID	WORKFLOW_ID
Ticket.WorkflowName	WORKFLOW_NAME

note

Note: NOTIFY is declared in the schema but is used for ticket create/update payloads; it is not populated during sync.

People

Source Field Name	SDM Attribute
People.AboutMe	ABOUT_ME
People.AlternateID	ALTERNATE_ID
People.ApplyTechnicianSignatureToReplies	APPLY_TECHNICIAN_SIGNATURE_TO_REPLIES
People.ApplyTechnicianSignatureToUpdatesAndComments	APPLY_TECHNICIAN_SIGNATURE_TO_UPDATES_AND_COMMENTS
People.AuthenticationProviderID	AUTHENTICATION_PROVIDER_ID
People.AuthenticationUserName	AUTHENTICATION_USER_NAME
People.BEID	BEID
People.BEIDInt	BEIDINT
People.Company	COMPANY
People.CostRate	COST_RATE
People.DefaultAccountID	DEFAULT_ACCOUNT_ID
People.DefaultAccountName	DEPARTMENT
People.DefaultPriorityID	DEFAULT_PRIORITY_ID
People.DefaultPriorityName	DEFAULT_PRIORITY_NAME
People.DefaultRate	DEFAULT_RATE
People.EndDate	END_DATE
People.ExternalID	EXTERNAL_ID
People.Fax	FAX
People.FirstName	FIRST_NAME
People.FullName	NAME
People.HomeAddress	HOME_ADDRESS
People.HomeCity	HOME_CITY
People.HomeCountry	HOME_COUNTRY
People.HomePhone, People.WorkPhone, People.MobilePhone, People.OtherPhone, People.PrimaryPhone	PHONE_NUMBERS
People.HomeState	HOME_STATE
People.HomeZip	HOME_ZIP
People.IMHandle	IM_HANDLE
People.IMProvider	IM_PROVIDER
People.IsActive	STATUS
People.IsActive	IS_ACTIVE
People.IsCapacityManaged	IS_CAPACITY_MANAGED
People.IsConfidential	IS_CONFIDENTIAL
People.IsEmployee	IS_EMPLOYEE
People.LastName	LAST_NAME
People.LocationID	LOCATION_ID
People.LocationName	LOCATION_NAME
People.LocationRoomID	LOCATION_ROOM_ID
People.LocationRoomName	LOCATION_ROOM_NAME
People.MiddleName	MIDDLE_NAME
People.Nickname	NICK_NAME
People.Pager	PAGER
People.PrimaryClientPortalApplicationID	PRIMARY_CLIENT_PORTAL_APPLICATION_ID
People.PrimaryEmail, People.AlternateEmail, People.AlertEmail	EMAILS
People.ProfileImageFileName	PROFILE_IMAGE_FILE_NAME
People.ReferenceID	REFERENCE_ID
People.ReportsToFullName	REPORTS_TO
People.ReportsToUID	REPORTS_TO_UID
People.ReportTimeAfterDate	REPORT_TIME_AFTER_DATE
People.ResourcePoolID	RESOURCE_POOL_ID
People.ResourcePoolName	RESOURCE_POOL_NAME
People.Salutation	SALUTATION
People.SecurityRoleID	SECURITY_ROLE_ID
People.SecurityRoleName	SECURITY_ROLE_NAME
People.ShouldReportTime	SHOULD_REPORT_TIME
People.TechnicianSignature	TECHNICAL_SIGNATURE
People.Title	JOB_TITLE
People.TypeID	TYPE_ID
People.TZID	TZID
People.TZName	TZNAME
People.UID	UID
People.UserName	USERNAME
People.WorkableHours	WORKABLE_HOURS
People.WorkAddress	WORK_ADDRESS
People.WorkCity	WORK_CITY
People.WorkCountry	WORK_COUNTRY
People.WorkState	WORK_STATE
People.WorkZip	WORK_ZIP

Group

Source Field Name	SDM Attribute
Group.CreatedDate	SOURCE_CREATED_DATE
Group.Description	DESCRIPTION
Group.ExternalID	EXTERNAL_ID
Group.ID	UID
Group.IsActive	STATUS
Group.ModifiedDate	SOURCE_LAST_MODIFIED
Group.Name	NAME

Location

Source Field Name	SDM Attribute
Location.Address	ADDRESS
Location.AssetsCount	ASSETS_COUNT
Location.City	CITY
Location.ConfigurationItemsCount	CONFIGURATION_ITEMS_COUNT
Location.Country	COUNTRY
Location.CreatedDate	SOURCE_CREATED_DATE
Location.CreatedFullName	CREATED_FULL_NAME
Location.CreatedUid	CREATED_UID
Location.Description	DESCRIPTION
Location.ExternalID	EXTERNAL_ID
Location.ID	UID
Location.IsActive	IS_ACTIVE
Location.IsRoomRequired	IS_ROOM_REQUIRED
Location.Latitude	LATITUDE
Location.Longitude	LONGITUDE
Location.ModifiedDate	SOURCE_LAST_MODIFIED
Location.ModifiedFullName	MODIFIED_FULL_NAME
Location.ModifiedUid	MODIFIED_UID
Location.Name	NAME
Location.PostalCode	POSTAL_CODE
Location.RoomsCount	ROOMS_COUNT
Location.State	STATE
Location.TicketsCount	TICKETS_COUNT
Location.UsersCount	USERS_COUNT

Asset

Source Field Name	SDM Attribute
Asset.AcquisitionDate	ACQUISITION_DATE
Asset.AppID	APP_ID
Asset.AppName	APP_NAME
Asset.ConfigurationItemID	CONFIGURATION_ITEM_ID
Asset.CreatedDate	SOURCE_CREATED_DATE
Asset.CreatedFullName	CREATED_FULL_NAME
Asset.CreatedUid	CREATED_UID
Asset.ExpectedReplacementDate	EXPECTED_REPLACEMENT_DATE
Asset.ExternalID	EXTERNAL_ID
Asset.ExternalSourceID	EXTERNAL_SOURCE_ID
Asset.ExternalSourceName	EXTERNAL_SOURCE_NAME
Asset.FormID	FORM_ID
Asset.FormName	FORM_NAME
Asset.ID	UID
Asset.LocationID	LOCATION_ID
Asset.LocationName	LOCATION_NAME
Asset.LocationRoomID	LOCATION_ROOM_ID
Asset.LocationRoomName	LOCATION_ROOM_NAME
Asset.MaintenanceScheduleID	MAINTENANCE_SCHEDULE_ID
Asset.MaintenanceScheduleName	MAINTENANCE_SCHEDULE_NAME
Asset.ManufacturerID	MANUFACTURER_ID
Asset.ManufacturerName	MANUFACTURER_NAME
Asset.ModifiedDate	SOURCE_LAST_MODIFIED
Asset.ModifiedFullName	MODIFIED_FULL_NAME
Asset.ModifiedUid	MODIFIED_UID
Asset.Name	NAME
Asset.OwningCustomerID	OWNING_CUSTOMER_ID
Asset.OwningCustomerName	OWNING_CUSTOMER_NAME
Asset.OwningDepartmentID	OWNING_DEPARTMENT_ID
Asset.OwningDepartmentName	OWNING_DEPARTMENT_NAME
Asset.ParentID	PARENT_ID
Asset.ParentName	PARENT_NAME
Asset.ParentSerialNumber	PARENT_SERIAL_NUMBER
Asset.ParentTag	PARENT_TAG
Asset.ProductModelID	PRODUCT_MODEL_ID
Asset.ProductModelName	PRODUCT_MODEL_NAME
Asset.PurchaseCost	PURCHASE_COST
Asset.RequestingCustomerID	REQUESTING_CUSTOMER_ID
Asset.RequestingCustomerName	REQUESTING_CUSTOMER_NAME
Asset.RequestingDepartmentID	REQUESTING_DEPARTMENT_ID
Asset.RequestingDepartmentName	REQUESTING_DEPARTMENT_NAME
Asset.SerialNumber	SERIAL_NUMBER
Asset.StatusID	STATUS_ID
Asset.StatusName	SOURCE_STATUS
Asset.StatusName	STATUS
Asset.SupplierID	SUPPLIER_ID
Asset.SupplierName	SUPPLIER_NAME
Asset.Tag	TAGS
Asset.Uri	URL

Configuration Item

Source Field Name	SDM Attribute
ConfigurationItem.AppID	APP_ID
ConfigurationItem.AppName	APP_NAME
ConfigurationItem.BackingItemID	BACKING_ITEM_ID
ConfigurationItem.BackingItemType	BACKING_ITEM_TYPE
ConfigurationItem.CreatedDateUtc	SOURCE_CREATED_DATE
ConfigurationItem.CreatedFullName	CREATED_FULL_NAME
ConfigurationItem.CreatedUid	CREATED_UID
ConfigurationItem.ExternalID	EXTERNAL_ID
ConfigurationItem.ExternalSourceID	EXTERNAL_SOURCE_ID
ConfigurationItem.ExternalSourceName	EXTERNAL_SOURCE_NAME
ConfigurationItem.FormID	FORM_ID
ConfigurationItem.FormName	FORM_NAME
ConfigurationItem.ID	UID
ConfigurationItem.IsActive	IS_ACTIVE
ConfigurationItem.IsSystemMaintained	IS_SYSTEM_MAINTAINED
ConfigurationItem.LocationID	LOCATION_ID
ConfigurationItem.LocationName	LOCATION_NAME
ConfigurationItem.LocationRoomID	LOCATION_ROOM_ID
ConfigurationItem.LocationRoomName	LOCATION_ROOM_NAME
ConfigurationItem.MaintenanceScheduleID	MAINTENANCE_SCHEDULE_ID
ConfigurationItem.MaintenanceScheduleName	MAINTENANCE_SCHEDULE_NAME
ConfigurationItem.ModifiedDateUtc	SOURCE_LAST_MODIFIED
ConfigurationItem.ModifiedFullName	MODIFIED_FULL_NAME
ConfigurationItem.ModifiedUid	MODIFIED_UID
ConfigurationItem.Name	NAME
ConfigurationItem.OwnerFullName	OWNER_FULL_NAME
ConfigurationItem.OwnerUID	OWNER_UID
ConfigurationItem.OwningDepartmentID	OWNING_DEPARTMENT_ID
ConfigurationItem.OwningDepartmentName	OWNING_DEPARTMENT_NAME
ConfigurationItem.OwningGroupID	OWNING_GROUP_ID
ConfigurationItem.OwningGroupName	OWNING_GROUP_NAME
ConfigurationItem.TypeID	TYPE_ID
ConfigurationItem.TypeName	TYPE_NAME
ConfigurationItem.Uri	URL

Account

Source Field Name	SDM Attribute
Account.Address1	ADDRESS_1
Account.Address2	ADDRESS_2
Account.Address3	ADDRESS_3
Account.Address4	ADDRESS_4
Account.City	CITY
Account.Code	CODE
Account.Country	COUNTRY
Account.CreatedDate	SOURCE_CREATED_DATE
Account.Fax	FAX
Account.ID	UID
Account.ID	ACCOUNT_ID
Account.IndustryID	INDUSTRY_ID
Account.IndustryName	INDUSTRY_NAME
Account.IsActive	STATUS
Account.IsActive	IS_ACTIVE
Account.ManagerFullName	MANAGER_FULL_NAME
Account.ManagerUID	MANAGER_UID
Account.ModifiedDate	SOURCE_LAST_MODIFIED
Account.Name	ACCOUNT_NAME
Account.Notes	NOTES
Account.ParentID	PARENT_ID
Account.ParentName	PARENT_NAME
Account.Phone	PHONE
Account.PostalCode	POSTAL_CODE
Account.StateAbbr	STATE_ABBR
Account.StateName	STATE_NAME
Account.Url	URL

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Ticket

Operation options

Option	Type	Default	Description
status	Comma-separated status names; resolved to status IDs via api/{appId}/tickets/statuses and applied as StatusIDs.	New,In Process

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/{applicationId}/tickets/search
• Default filters: ModifiedDateFrom applied on incremental sync when a since token is supplied; optional StatusIDs when the status option is set

People

Operation options

Option	Type	Default	Description
isActive	Restrict results to active people.	true

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/people/search
• Default filters: isActive=true (from the isActive option, default true)

Group

Operation options

Option	Type	Default	Description
isActive	Restrict results to active groups.	true

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/groups/search
• Default filters: isActive=true (from the isActive option, default true)

Location

Operation options

Option	Type	Default	Description
isActive	Restrict results to active locations.	true

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/locations/search
• Default filters: isActive=true (from the isActive option, default true)

Asset

Operation options

Option	Type	Default	Description
status_ids	Comma-separated status IDs, applied as StatusIDs.	669,727

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/{appId}/assets/search
• Default filters: optional StatusIDs when the status_ids option is set; ModifiedDateFrom applied on incremental sync when a since token is supplied

Configuration Item

Operation options

Option	Type	Default	Description
isActive	Restrict results to active configuration items.	Default true
type_ids	Comma-separated type IDs, applied as TypeIDs.	1,2

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/{appId}/cmdb/search
• Default filters: isActive=true (from the isActive option, default true); optional TypeIDs when the type_ids option is set

Account

Operation options

Option	Type	Default	Description
isActive	Restrict results to active accounts.	true

Delta sync

The connector README does not document sync behavior for this object.

API

• Type: REST endpoint · Endpoint: POST api/accounts/search
• Default filters: isActive=true (from the isActive option, default true)

Changelog

Changelog

The TeamDynamix connector has undergone the following changes:

Version	Description	Migration Steps
3.0.6	New Features - Added support for synchronizing Account/Department records from TeamDynamix, so organizational accounts and departments are now available in Brinqa alongside the other TeamDynamix data. - Ticket records now include the ticket Description, giving fuller context on each synchronized ticket.	N/A
3.0.5	Bug Fixes - Corrected the way ticket attributes are mapped when creating or updating tickets back in TeamDynamix. Standard fields (such as status, URL, created/modified dates) and custom attributes are now translated to the correct TeamDynamix field names, so write-back operations apply the intended values reliably.	N/A
3.0.4	Improvements Dependency Upgrades Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	N/A
3.0.3	Improvements - The connector now detects when its authentication token has expired and automatically requests a new one. This avoids intermittent authentication failures during long-running synchronizations.	N/A
3.0.2	Improvements - Aligned the API URL handling so the configured TeamDynamix Web API base path is used consistently across all requests. Bug Fixes - Corrected the data types of several asset and people attributes (for example, purchase cost, default rate, cost rate, and workable hours now store decimal values; requesting department ID, default priority ID, work zip, and "is room required" now store text) so values that previously failed to map are now captured accurately.	• Asset / People / Location: The stored data type changed for several attributes (such as purchase cost, requesting department ID, default rate, cost rate, workable hours, default priority ID, work zip, and "is room required"). Re-sync these models so existing records are repopulated with the corrected values.
3.0.1	New Features - Expanded the connector beyond tickets to synchronize additional TeamDynamix data: Assets, Configuration Items, Groups, Locations, and People. This brings TeamDynamix asset inventory and organizational data into Brinqa.	N/A
3.0.0	Overview The TeamDynamix connector integrates with the TeamDynamix IT Service Management platform to synchronize service-desk ticket data into Brinqa. It also supports creating and updating tickets back in TeamDynamix. Category: IT Service Management Models	N/A