Select Multiple CI's

Greetings,

We have a few forms that will require selecting multiple CI's (I.E. Submitting Audit Findings that affect multiple VM's) and can't seem to find a way to associate a Ticket with Multiple CI's.   I don't see a way to make this a 1 to Many relationship so is the only way to do this is by creating a series of CI fields that essentially do the same thing with a dependency question of "Do you have more assets to associate with this ticket?" Question.   

I'm beginning to think that I'm going down the wrong path here as this is starting to become a logistical nightmare and wanted to reach out and see what the best practice is from TDX on how to associate a ticket with multiple CI's

Thank you!

Tags forms Configuration-Items
Asked by Rik Miller on Fri 6/30/23 7:20 PM
Sign In to leave feedback or contribute an answer

Answers (3)

This answer has been marked as the accepted answer
Rik Miller Fri 9/8/23 7:26 PM

We ended up updating our process to create both Configuration Items first and then add the relationship after creation.

No feedback
Mark Sayers Wed 7/5/23 9:28 AM

Hello Rik,

There's not an easily dynamic way to produce more fields in the TeamDynamix forms feature, unfortunately. In the standard Assets field, as long as it isn't being filtered in the form-builder in a way that would exclude them, you *can* select multiple CIs at once. Have you tried doing that with a user that has full access to the Assets/CIs application in your environment?

Sincerely,
Mark Sayers
Sr Support Consultant, CS

No feedback
Mark, We can see multiple CI types in the list but we are looking to multi select multiple CI's. As an example we may receive an audit finding that affects multiple Virtual Machines (CI) where we would like to create a single ticket for the Audit Finding and associate said ticket with multiple Virtual Machine CI's on the same ticket. The only solution that I see currently is to create a duplicate ticket for each VM that this affects which becomes a logistical and maintenance nightmare.

Thoughts... - Rik Miller Wed 7/5/23 2:18 PM
Again, you *should* be able to do this via either the standard Asset/CI field on a ticket's form during creation or from the Assets/CIs tab on a ticket. When you enter the Asset/CI lookup window, just filter its results by the CI Types that are *not* "All Assets" so you're only seeing results that are CIs. Then in the results portion of the page, there are checkboxes to allow for selecting multiple CIs to associate with your ticket. - Mark Sayers Wed 7/5/23 2:52 PM
That's not my experience. Feel like I must be missing something. - David Tod Wed 7/5/23 3:15 PM
on the Assets tab, yes, but not the form - David Tod Wed 7/5/23 3:18 PM
Are you first clearing out all of the filter options from the Asset Filtering portion of the lookup page? - Mark Sayers Wed 7/5/23 3:20 PM
Ah sorry on the form it might not be possible currently. I didn't realize that behavior was different, but it does seem to be different. - Mark Sayers Wed 7/5/23 3:21 PM
David Tod Wed 7/5/23 9:25 AM

Interested in this question too. We're thinking about CIs for access requests, but this could be challenging. I'm sure we could build it in iPaaS though.

No feedback