Adding Custom Lookups to the Lookup Tool in Helpdesk
Have you ever created a custom lookup, following the Altiris product documentation, only to have to touch SQL to make future modifications to the lookup? This article will show you the simple steps needed to add your custom created lookup to the lookup admin tool within the Altiris Helpdesk flyout menu.
Begin by taking a backup of your Altiris_Incidents database in case you run into any difficulties.
After you've backed up your database, follow the Altiris product guide to create your custom lookup. Once your initial lookup is complete, go into SQL. Expand the Altiris_Incidents database, and then expand tables. Next look for the table dbo.lookup_info. This is the table that we will be working with.
At this point, you can write a query or you can add a new line directly to the table. For the sake of speed in writing this document, I will just open the table and add directly to it.
Click in the last line that is populated with all NULLS.
I am breaking this up into several sections so that you can see everything that needs to be added. Basically, you will copy the formatting of the items above, leaving the lookup_info_guid blank. The guid will create itself when we finish entering the information.
Begin by assigning an id number under the lookup_info_id column. Next, skip the guid and go to enter the lookup_info_display_name - do this by following the format below by replacing the word custom with your lookup's name. The value of this will be defined later in a string. Now, specify the lookup_info_values_source - this will be actual lookup table.
Our next step is to specify the lookup_info_table_name. Assuming you placed your lookup in the workitem table, this will be workitem. Next enter the lookup_info_field_name and column name of your lookup as it appears in the workitem table. Next set the lookup_info_view_format by once again following the format of the previous entries. Finally, set the status and the lookup_info_is_ordered column to 0.
Once you are done, click to a new line and your guid will be generated.

Now that we've done the necessary work in the Altiris_Incidents database, close SQL. Go to your custom.config file and add the following string. Again, replace custom with your own values.
<strings> <string id="sid_workitem_custom_lookup_value">Custom</string> </strings>
Save your custom.config file, close it, and restart IIS.
Now go to the admin flyout menu and select lookups.
You will now notice your lookup field here. You can now edit lookups, change the ordinal value, set active status, etc. just as you would with any other lookup.
We are done. The information that just entered is then called by the LookupList.ascx template. From this template, which allow us to manage the lookup various lookup lists.
| Attachment | Size |
|---|---|
| Adding Custom Lookups to the Lookup Tool in Helpdesk.doc | 88.5 KB |
- Login or register to post comments
- 4391 reads
- Printer-friendly version






















Additional Functionality
It appears that a byproduct of this procedure is that you gain the ability to use pickers within the various rules.
As an example go to incident rules. Under the criteria, click on the drop-down list. You should notice that your custom lookup is there as well.
The part that I like is when you select the "is one of option"...no more looking up id's in the table, just check the boxes of the ones you want.
Validation rule on custom lookups
Great info...
Any idea on how to get the custom lookup fields in the pickers for the business rules?
Advanced assignments is how I apply rules to custom fields, but have never figured out how to add them to the picker within the rules for selection by the customer.
Thanks
adding to the rules
you can add them, but i don't know how it works. here's how i've got it to work. add the field you want through an advanced assignment then save your rule. once you go back in and edit the lookup you specified in the advanced assignment, the picker will be available for you. i'm not sure how you load it initially, but for some reason when you add it manually, then go back and edit -- the lookups will be there.
If I understand this right,
If I understand this right, you do not see non-workitem lookups in the dropdown lists. I believe this is because the IncidentLookupListAll item from the query table limits itself to lookup_info_table_name = 'workitem'. If you remove that bit, your custom contact and managed_object lookups will appear.
Excellent work! I created a
Excellent work! I created a custom lookup with a boatload of info to choose from. This makes it so much easier to administer!
Great work Dave!
this was very useful for
this was very useful for me--thank you!