Skip to content
TheChatArchiveThe Chat Archive
gpt-4-turbo-2024-04-09· OpenAIAi2 WildChat-4.8M (AI2)

In servicenow, i have a reference field called asset on Ritm and sctask table. My…

  1. User

    In servicenow, i have a reference field called asset on Ritm and sc_task table. My requirement is when i click on asset field it will show records in ritm records and view is asset but same field doesn't show any record on sc_task form EUS view. How to solve this problem. Give complete step by step

  2. Assistant

    To solve the issue where the reference field 'asset' behaves differently in two different forms/views (RITM and sc_task tables) in ServiceNow, you can follow these steps to configure the behavior differently depending on the context (view or form). The likely root cause is view-specific configurations or ACLs impacting the display of the reference field in different views.

    Step-by-Step Guide

    1. Verify the Configuration of the Asset Field in Both Forms

    Firstly, check if the reference field has any view-specific configurations or scripts applied:

    • Navigate to the Form Configuration:

      1. Go to the respective tables (sc_req_item for RITM and sc_task).
      2. Open any record.
      3. Right-click on the form header and select "Configure" -> "Form Layout".
    • Check the Asset field settings to ensure it is added to the forms and see if there are any differences in settings like view rules or UI policies.

    2. Inspect ACLs on the Asset Field

    Access Control Lists (ACLs) might be restricting visibility:

    • Check ACLs:
      1. In the filter navigator, search for "Access Control (ACL)".
      2. Search for ACLs that apply to the Asset field specifically and compare any differences between the sc_req_item and sc_task tables.

    3. Update or Create View-Specific ACLs

    If necessary, you may need to adjust or create new ACLs to handle view-specific permissions:

    • Modify or Create an ACL:
      1. Go to Access Controls and edit/create an ACL for the asset field where the table is sc_task.
      2. Define the ACL by setting the required permissions, and make sure to set the correct view (EUS).

    4. Verify Reference Qualifiers

    Reference Qualifiers can restrict which records are displayed in a reference field:

    • Check/Modify Reference Qualifiers:
      1. Again, go to Form Design by opening a record and right-clicking on the form header.
      2. Find the asset field, and click on the Advanced view if available.
      3. Check the Reference Qualifier to see if there are any conditions or scripts that could behave differently based on the view.

    5. Check for View-Specific Scripts/UI Policies

    Sometimes custom scripts or UI policies are applied to views:

    • Inspect Scripts and Policies:
      1. Search for "UI Policies" and "Business Rules" in the navigator.
      2. Check for any scripts or policies that might be applying only to the sc_task table in the EUS view.

    6. Testing Changes

    After making changes, always ensure to test both views:

    • Open records in both sc_task and RITM in the respective views.
    • Verify that the asset field behaves as expected in both areas.

    7. Clear Cache and Sessions

    Sometimes, changes don’t reflect immediately due to caching:

    • Clear cache: Log out, clear browser cache, or use an incognito window to test the changes.

    Final Note

    If configuration changes are being made in a production instance, consider testing in a development or staging instance first. If the configuration appears complex or risky, involving a ServiceNow administrator or consultant would be advisable to ensure compliance and operational continuity.

    By following these steps, you should be able to configure the asset reference field in ServiceNow to behave appropriately for different tables and views. Remember, changes in major platforms like ServiceNow can have large impacts if not thoroughly tested.

  3. User

    I cant find anything

  4. Assistant

    If you’ve checked all the likely configurations (including Form Layouts, ACLs, Reference Qualifiers, UI Policies, and Business Rules) and still see no differences or solves, it might be helpful to inspect possibly subtler aspects of the configuration. Here’s a deeper step-by-step approach to further troubleshooting or validating settings, which could be affecting the visibility of assets in your sc_task form within the EUS view:

    Step-by-Step Deeper Dive

    1. Recheck View-Specific Forms

    Sometimes, form views can be overlooked. Confirm that you are modifying the correct form view:

    • Open an sc_task record.
    • Right-click on the form header and select "Configure" -> "Form Layout".
    • Carefully check the view selected in the dropdown present at the top left of the dialog. Ensure you are working on the EUS view.

    2. Script Includes or Client Scripts

    Check if there are any Script Includes or Client Scripts specific to the view or table that manipulate reference fields:

    • Client Scripts:

      1. Go to System Definition > Client Scripts.
      2. Filter by table (sc_task) and check if there are scripts affecting the asset field.
    • Script Includes:

      1. Go to System Definition > Script Includes.
      2. Search for scripts that are executed for the sc_task form operations which might impact the reference population.

    3. Reassess Reference Field Properties

    There could be details in the asset reference field properties affecting visibility:

    • Field Properties:
      1. In Form Layout, click the gear icon next to the asset field.
      2. Check properties like "Attributes,” which might have parameters such as ref_contributions affecting functionality.

    4. Analyze Dictionary Entries

    The dictionary for the field might have conditions or attributes setting behavior for the field:

    • Dictionary:
      1. Go to System Dictionary.
      2. Search for entries for the asset field tied to the sc_task table specifically.
      3. Review conditions or attributes set there.

    5. Re-examine Data Policies

    Data policies can affect data visibility on forms:

    • Data Policies:
      1. Navigate to Data Policy > Policies.
      2. Check for policies affecting sc_task and reference fields.

    6. Additional Layers of Customization

    Investigate other customizations such as UI pages, embedded widgets, or advanced conditional formatting scripts, which might be less obvious but could influence the rendering:

    • Embedded Solutions:
      1. Consider whether there are any customized embedded pages or widgets within the form.
      2. Review any conditions or coding therein that might impact data displays.

    7. Consult Logs and Debug

    If these configurations yield no clues, proceed to look into error logs or debugging:

    • Error Logs:
      1. Check logs under System Logs > All Logs for errors when accessing the sc_task form in EUS view.
    • JavaScript Debugging:
      1. Open the browser’s developer console.
      2. Check for any console errors or warnings when loading the EUS view on sc_task.

    8. Community and Support

    If local analysis doesn't resolve the issue, consider posting the issue in ServiceNow community forums or reaching out to ServiceNow technical support for more specific aid.

    Final Recommendations

    Be meticulous with every step. Sometimes, settings or configurations that impact functionality can be deeply nested or not apparent without a detailed inspection. If the system is considerably customized or the issue persists, getting a second pair of eyes from a colleague or a consultant specializing in ServiceNow might uncover overlooked configurations or custom code affecting the behavior.