> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/flex-modes/change-your-analysis/change-the-properties.md). # Change the properties Use the Properties menu to change the property columns that display in the grid. {% hint style="info" %} User permission: **Query** > **Change properties** You must select a dimension to activate the **Properties** menu; it isn't available in Summary view. {% endhint %} Properties are information stored about a dimension. By default, the **Code** and **Name** property columns display for all dimensions. The available properties depend on the selected dimension and underlying database. For example, you might have an Address property for a Customer dimension or a Unit of Measure property for the Product dimension. 1. Click the **Properties** menu. 2. Select the properties you want to view and clear the properties you don't want. You must have at least one property selected. 3. Click anywhere outside the **Properties** menu to close it. The grid updates as you select or clear properties. If you select multiple properties, the **Properties** menu displays a summary. Hover over the menu to see all the selected properties. Your property selections remain until you reset the grid.

Code and Name property columns displaying in the grid

{% hint style="success" %} If you need to scroll horizontally to view all the columns, freeze the property columns to keep them in view. If you frequently edit the default properties, save your view as a favorite to keep your property selection(s) for later. To return to the default view, click **Reset**. {% endhint %} ### Example 1: Identify each customer's country and sales rep Add properties to see where each customer is located and their sales representative. 1. Click the **Customer** dimension, for example, **Customer Ship To**. 2. Add the **Country** and **Sales Rep** properties and clear **Code**.

Customer name, Country and Sales Rep name property columns displaying in the grid

### Example 2: Get more details on declining customers Identify the customers who are declining the most in the year to date and add properties to view useful details, such as their contact information. 1. Click **Mode** > **Variance**. 2. Click the **Customer** dimension, for example, **Customer Ship To**. 3. Sort the **Variance** value column in ascending order. The worst performing customers display at the top of the grid. 4. Select and focus on the ten worst-performing customers (top ten in the grid). 5. Add properties such as **Country**, **Email** and **Phone**. The property columns display in the grid, allowing you to see the contact details for those declining customers.

Country and contact details displaying alongside the customer data

### Example 3: Use properties like dimensions Use a property like a dimension to analyze data by information that isn't available as a dimension. For example, suppose you want to analyze the Sales data according to the suburbs in which your customers are located but you do not have a Suburb dimension. 1. Choose your preferred mode, for example, **Variance**. 2. Click the **Territory** dimension, then select and focus on the territory you're interested in, for example, **California** in the **USA**. 3. Click the **Customer** dimension, for example, **Customer Ship To**. 4. Add the **Suburb** property and remove all other properties.

Customers grouped by suburb, as if you had selected a Suburb dimension

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.phocassoftware.com/flex-modes/change-your-analysis/change-the-properties.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.