Articles in this section

How to Rename a Dataset Field in the Bold Reports Query Designer

Published:
Updated:

Renaming a dataset field in the Bold Reports® Web Report Designer can make report fields easier to recognize, especially when source-system names are abbreviated or unclear to users. Clear field names make reports easier to build and maintain; update expressions that refer to the old name so report items continue to work.

Steps to Rename a Dataset Field

Step 1: Open the Data Pane

  • In the Web Report Designer, open the configuration panel and click the Data icon to view the available datasets.
    Open Data Pane

Step 2: Edit the Dataset

  • Locate the dataset that contains the field you want to rename. Click the More Options (ellipsis) icon next to the dataset name and select Edit to open the Query Designer.
    Edit Dataset

Step 3: Rename the Field

  1. In the visual Query Designer, locate the field in the selected fields list.
  2. Double-click the field name.
  3. Enter the new name and press Enter to save the change.
    Rename Field

This step describes renaming the selected field in the visual Query Designer. Confirm whether the change updates the query’s output alias or only the dataset field name, and whether the same operation is supported in code (text) mode, for your designer version.

Step 4: Save the Changes

  • Click Finish in the lower-right corner of the Query Designer to apply the change and update the dataset schema.
    Save Changes

    Update Expressions That Use the Old Name : Review the report for expressions that refer to the old field name, such as Fields!OldName.Value, and replace those references with the new field name. An expression that continues to use the old name may produce an error or fail to display the expected value.

Step 6: Preview the Report

  • Click Preview on the top toolbar and verify that the report items using the renamed field display correctly.
    Preview Report

Related Articles

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied