Hey @Rooma1
Please find the solution
Potential Issues:
- Missing GlideRecord Initialization: The script doesn't explicitly create or initialize a GlideRecord object (gr) before adding queries.
- Incorrect Field Name (Maybe): Depending on your specific table structure, the field name for marking a location as inactive might be different. Double-check the actual field name used in your Incident table.
var gr = new GlideRecord('incident_location'); // Replace with actual location table if different
// Use 'getDisplayValue' to handle multiple words in location names (optional)
var locationValue = g_form.getValue('location').getDisplayValue();
// Consider using 'OR' operator for better performance with many inactive locations
gr.addQuery('name','STARTSWITH',locationValue);
gr.addOrQuery('inactive','true'); // Replace 'inactive' with the actual field name
gr.query();
if (gr.hasNext()) {
g_form.setValue('show all locations', true);
}
Explanation of Improvements:
- Initializes a GlideRecord object (gr) with the appropriate table name (replace 'incident_location' if your location table has a different name).
- Uses getDisplayValue on the location field value to handle cases where the location name might contain multiple words. This ensures the filter considers the entire displayed value.
- Considers using the OR operator in the addOrQuery method for improved performance, especially if you have a large number of inactive locations.
Additional Considerations:
- Make sure the UI Macro is associated with the 'Location' field on the Incident form.
- If the issue persists, check the UI Macro properties to ensure it has the appropriate read access on the 'incident_location' table (or your actual location table).
By implementing these adjustments, your UI Macro script should effectively create a custom filter on the 'Location' field, allowing users to see both active and inactive locations in the lookup.
Thanks
Aravind Panchanathan
