--- title: "Set up validation rule of type Configurable lookup - Web service" slug: "set-up-validation-rule-of-type-configurable-lookup-web-service" description: "Learn to set up configurable lookup validation rules using web services to ensure data quality and compliance with defined standards effectively." tags: ["Task topic"] updated: 2026-03-20T11:31:17Z published: 2026-03-20T17:44:40Z canonical: "docs.staedean.com/set-up-validation-rule-of-type-configurable-lookup-web-service" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up validation rule of type Configurable lookup - Web service Use validation rules to check if the data is in line with the defined standards. To validate data, you can use several validation types. This topic explains how to set up a configurable lookup validation rule with a configurable lookup of type '**Web service**'. Use a: - Configurable lookup validation to add a custom lookup to a field and to validate if the field value matches a value as defined by the configurable lookup. - Configurable lookup of type '**Web service**' to get the possible options of a field from a web service. You can add validation rules in these ways: - Manually. - Select the fields to be validated from a page. > [!NOTE] > Note > > - If the field to which the configurable lookup is applied, already has a lookup, the configurable lookup overwrites the existing lookup. > - Before you can set up a configurable lookup validation rule, set up the configurable lookup to be used. ### Steps 1. Click **Data quality management**. 2. On the **Data quality policies** tab, in the list, click the link of the desired data quality policy. > [!NOTE] > Note > > If you want to edit another data quality policy version than the currently shown version, first select the desired version. To do so, on the **Action Pane**, on the **Version** tab, click **Versions**. On the dialog, select the desired version and click **OK**. 3. Sub-task: Manually create validation rule. 1. You can manually create a validation rule and define the table and field which value must be validated. On the **Validation rules** tab, click **Add**. 2. Define the table of the field which value must be validated. In the **Table** field, enter or select a value. > [!NOTE] > Note > > If you want to validate field values in inherited tables, define the child table instead of the base table. For example, instead of DirPartyTable, use DirOrganization or DirPerson. 3. Define the field which value must be validated. In the **Field** field, enter or select a value. 4. Sub-task: **Create validation** rules by selecting fields. 1. You can create validation rules by selecting the fields, which value must be validated, from a page. On the **Validation rules** tab, click **Select fields**. 2. Open the page from which you want to select fields. 3. On the **Field picker** dialog, click **Select fields**. 4. Click the **'+'** button for each field that you want to select. 5. On the **Field picker** dialog, click **Done**. 6. On the **Field picker** dialog, click **Submit** to save the selected fields to the validation rule. 5. Define to which records the validation rule is applied. You can apply a validation rule to: In the **Record type** field, select an option. - New records only. - Existing records only. - New records and existing records. 6. In the **Validation type** field, select '**Configurable lookup**'. 7. Define when the validation rule is applied: In the **Event** field, select an option. > [!NOTE] > Note > > The configurable lookup is added to the defined field when the page is opened. - **Field**: The validation rule is applied just before the standard field validation is done. - **Record**: The validation rule is applied just before the standard record validation is done. 8. Define what is done if the validation rule is not met: In the **Outcome** field, select an option. > [!NOTE] > Note > > For each validation rule, you can define a message to be shown. If you do not define a validation rule message, in case of a warning or error, a default message is shown. - **Warning**: A warning message is shown. The record or the field value is saved. - **Error**: An error message is shown. The record or the field value is not saved. - **No validation**: Only the configurable lookup is added to the field. No validation is done. **Example**: You can use the configurable lookup to show a list with often-used values for the field. However, you can enter other values as well. 9. In the **Configurable lookup** field, enter or select a configurable lookup of type '**Web service**'. 10. Sub-task: Set up a request parameter override of type **Field**. 1. For a web service, parameters can be set up. If so, these parameters are shown on the **Properties** tab. For **Request parameters**, a default value can be defined. You can override this default value with the value of a field. If no default value is defined, do the same steps to define the request parameter value. On the **Properties** tab, for the desired **Request parameter**, select the **Override setup** check box. > [!NOTE] > Note > > If a **Custom request handler** is defined for the web service, no **Request parameters** are available. 2. In the **Parameter type** field, select '**Field**'. 3. In the **Field name** field, enter or select a value. > [!NOTE] > Note > > You can only select a field from the table that is defined for the validation rule. 11. Sub-task: Set up a request parameter override of type **Custom**. 1. For a web service, parameters can be set up. If so, these parameters are shown on the **Properties** tab. For **Request parameters**, a default value can be defined. You can override this default value with a value that is defined by a custom method. If no default value is defined, do the same steps to define the request parameter value. On the **Properties** tab, for the desired **Request parameter**, select the **Override setup** check box. > [!NOTE] > Note > > If a **Custom request handler** is defined for the web service, no **Request parameters** are available. 2. In the **Parameter type** field, select '**Custom**'. 3. Define the custom class that is used to define the parameter value. In the **Class name** field, enter or select a value. > [!NOTE] > Note > > You can only select classes that extend the **DQSWebServiceParametersBase** base class. This custom class must have a return method that returns a value. 4. Define the custom class return method that is used to define the parameter value. In the **Method name** field, enter or select a value. 12. Sub-task: Set up a request parameter override of type **Fixed value**. 1. For a web service, parameters can be set up. If so, these parameters are shown on the **Properties** tab. For **Request parameters**, a default value can be defined. You can override this default value with a fixed value. If no default value is defined, do the same steps to define the request parameter value. On the **Properties** tab, for the desired **Request parameter**, select the **Override setup** check box. > [!NOTE] > Note > > If a **Custom request handler** is defined for the web service, no **Request parameters** are available. 2. In the **Parameter type** field, select '**Fixed value**'. 3. In the **Parameter value** field, type a value. 13. Sub-task: Set up response parameter. 1. For a web service, parameters can be set up. If so, these parameters are shown on the **Properties** tab. Indicate which response parameters are used to define the configurable lookup values. For each of the response parameters used, set up a condition to define which response values from the web service are valid. A condition has a type and a value. For each of the response parameters used, the condition must be met. On validation, the process is: Result: The validation rule is only met if for each used response parameter, the condition is met. On the **Properties** tab, for the desired **Response parameter**, select the **Use as a response parameter** check box. > [!NOTE] > Note > > If a **Custom response handler** is defined for the web service, no **Response parameters** are available. 1. Send request to web service. 2. Web service gives response values. 3. Apply the condition for each used response value. 2. In the **Condition type** field, select an option. 3. In the **Parameter value** field, type a value. 14. Sub-task: Set up response parameter override. 1. For a web service, parameters can be set up. If so, these parameters are shown on the **Properties** tab. You can process a **Response** value, as received from the web service, before you use it to validate a value in D365 F&SCM. You can only do so with a custom class and method. On validation, the process is: Result: The validation rule is only met if for each used response parameter, the condition is met. On the **Properties** tab, for the desired **Response parameter**, select the **Override setup** check box. > [!NOTE] > Note > > - Select this check box for each response parameter for which you also select the **Use as response parameter** check box. > - If a **Custom response handler** is defined for the web service, no **Response parameters** are available. 1. Send request to web service. 2. Web service gives a response. 3. Process response with custom method. 4. Get response from custom method. 5. Apply the condition for each used response value. 2. Indicate which response parameters are used to define the configurable lookup values. For each of the used response parameters, set up a condition to define which response values from the custom method are valid. A condition has a type and a value. For each of the response parameters used, the condition must be met. Select the **Use as a response parameter** check box. > [!NOTE] > Note > > Select this check box for each response parameter for which you also select the **Override setup** check box. 3. Define the custom class that is used to process the web service response and that returns the value that is used as input for the condition. In the **Class name** field, enter or select a value. > [!NOTE] > Note > > You can only select classes that extend the **DQSWebServiceParametersBase** base class. This custom class must have a return method that returns a value. 4. Define the custom class return method that is used to process the web service response and that returns the value that is used as input for the condition. In the **Method name** field, enter or select a value. 5. Define the condition that is applied to the value that is returned by the custom class method. In the **Condition type** field, select an option. 6. In the **Parameter value** field, type a value. 15. Close the page. ## Related - [Set up validation rule of type Configurable lookup](/set-up-validation-rule-of-type-configurable-lookup-flow.md)