--- title: "Troubleshooting IQA configuration" slug: "troubleshoot-iqa-configuration" description: "Learn how to use specific options to troubleshoot the IQ Anywhere configuration." updated: 2024-04-17T14:58:15Z published: 2024-04-17T14:58:15Z canonical: "docs.zilliant.com/troubleshoot-iqa-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshoot IQA Configuration ## To troubleshoot an IQA Configuration If the **IQA Configuration** does not update the specified Deal Manager fields, use the following options to troubleshoot the configuration: - **Error Field** on the Line Items in the **IQA Configuration** record header—Captures error messages during an IQA call and provides a clue to solving a configuration issue. Default field name is **zpl__Error__c**. - **Enable Logging** in the **IQA Configuration** record header—Select this checkbox to capture IQA calls to the browser console. When logging is on, the IQA calls made when users add or edit lines in the **Edit Lines** modal are logged to the browser console. Logging includes the input JSON and the returned JSON, including any error codes. This logging can be used to find a number of conditions. For example: - If any unexpected parameter values are being passed into the IQA call. - If the parameters are spelled correctly. - If there is connection with the backend services via the error code. - If all formula values are being returned. ![IQA_Enable logging](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/IQA_Enable%20logging.png?sv=2026-02-06&spr=https&st=2026-11-18T05%3A48%3A59Z&se=2026-11-18T06%3A48%3A59Z&sr=b&sp=r&sig=Sv8eSwf2MlYPWtLUAB4k%2BvMx%2B6SMG%2BvkMD5csIoH7%2B0%3D) - **Is Disabled** on the **Parameter Mapping** record—Use this setting to start troubleshooting by sending a limited number of parameters with the call. By incrementally adding parameters to the list, it is possible to find the one that is causing the issue. Usually, you should use this setting together with disabling a **Formula Mapping** record and enabling logging of the call. - **Is Disabled** on the **Formula Mapping** record—Use this setting to start troubleshooting by requesting a limited number of formulas back with the call. By incrementally adding to the list, you can find the one causing the issue. Usually, you should use this setting with the **Is Disabled** setting on the **Parameter** record and enabling logging of the call. - **Literal Value** on the **Parameter Mapping** record—Use this setting to test if a specific parameter value is causing an issue by temporarily setting the value to **Literal Value** to see if the error resolves. A common issue with formula configuration is incorrect handling of null inputs. Passing literal values is a good way to find this issue.