TDNext Asset Importer - Assigning Owner via OrgID
Is there any way to assign the owner through asset import off of a simpler field? It is nearly impossible to generate the format that the importer wants for owner by pulling data from other systems and I'd like to just use the person objects Organizational ID as that is a consistent datapoint we use in multiple systems.
Our library has loaner laptops that we would like to keep track of via importing of a report from the library checkout system but the owner format that TDNext expects is excessively painful to generate in a report form another tool or even excel formulas without a high degree of issues on a number of records.
I really dont want to add a custom datapoint just to list the users ID#s from the import and have that be a less useful datapoint than having it tied to the user object but I dont see any other option if I cant associate an owner via a different method on import.
Answers (2)
Hi Justin,
Unfortunately the asset import feature built into the UI expects the Owner field's value to be in the following format:
Name <Alert/Notification Email>
I do realize this might not be easy to auto-populate, but if you download the import template from TDNext > your Assets/CIs app, the Owner field is prepopulated in the correct format with a choice list that include all users in your org.
Sincerely,
Mark Sayers
Sr Support Consultant, CS
My frustration with this 'download the import template from TDNext > your Assets/CIs app, the Owner field is prepopulated in the correct format with a choice list that include all users in your org' is we can't search for an Owner by name only. The dropdown requires us to enter the Owners in this format Name<Alert/Notification Email>
We need the option to enter only the Name. We spend too much time scrolling through Owner names.
Are we doing something wrong? I've attached an example.
The formatted version is important because of times when there’s more than one person with the same name. Unfortunately to change the requirement of that field's formatting would require an enhancement, so I do recommend submitting that to ask for a change to the import requirement for person fields in assets.
https://solutions.teamdynamix.com/TDClient/1965/Portal/Requests/ServiceDet?ID=2148
Sincerely,
Mark Sayers
Sr Support Consultant, CS - Mark Sayers Thu 4/11/24 4:09 PM