PhixFlow stores data in tables.

s are used to display the data in these tables, where only the information specified is shown.

1. Attributes

   1. Attributes from the base table
      Specify which attributes to include in your view. You can hide attributes that you want access to but do not necessarily want a user to see, such as the UID of a record.

   2. Attributes from related tables.
      These are the attributes available to the view as the table they originate from shares a relationship with the base table as defined in the ERDs; see Entity Relationship Diagrams. Views which contain these type of attributes are referred to as a relational view.

2. Records:

   1. For each table, the view includes records specified in the tables default period. This can be all data (usually for transactional data) or only the latest.

3. Sorting and Filtering

   1. You can filter and sort records. See Filtering and Sorting Data.

Data can be displayed in different ways.

1. : the attributes form the grid columns and data records are displayed in rows. PhixFlow can add scroll bars or paging where grids cannot be accommodated by the screen size.

2. : rather than using a form to display data, you can use a card. Any palette item can be added to a card which offered great flexibility.

3. : attributes are represented in different segments of a pie chart, with values aggregated to represent the segment size. 

4. : attributes are represented on the vertical axis, with values aggregated and represented in the bar length.

5. : attributes are represented on the horizonal axis, with values aggregated and represented in the bar height.

6. : attributes are represented as points on a horizontal axis, with values aggregated and setting the point position on the vertical axis.

7. : attributes are represented by different fields. Usually a form is linked to an action on a grid. For example, the application user selects a line on a grid, and the form displays the data from that record.

Form and card components are special data components, as they can contain other elements, usually fields and labels.

For more information on setting up charts and graphs, see Creating Dashboards and Reports.

1. There are several ways to show data on a screen:

   1. From an Entity Relationship Diagram (ERD), select a table and use the Create Screen option; see Creating a Screen from an ERD Table.

   2. Drag a Table from the repository or a tables icon from its properties directly onto a screen.

      1. A list of available tables is available by clicking the Tables button on the toolbar.

      2. This method will typically set the data for the backing form to that of the table.

2. PhixFlow asks you how you want the data to be displayed, select the desired option:

   Open

   

3. The data is added to the screen.

1. Drag attributes from the Available Attributes window onto the screen.

2. Start with attributes from the current (base) table.

   1. Optionally, click on related tables to show additional attributes that are available.

3. When you have dragged all the attributes you require, close the window.

4. Open

   

5. These attributes can be changed by selecting the 

    button in the toolbar to add new attributes or right-clicking and selecting
    to change existing attributes

   1. See Available Attributes Window for details.

Optionally, specify if you want to apply any filters or sort orders to the data:

Once you have created a view, you can reuse it in multiple locations. In the repository navigate the the table which owns the view, the base table, open the table and in the views section drag the desired view onto your screen. Be aware however that changes made to the view will affect all instances of that view.

When you drag attributes from the Attribute Selection window or table onto a form, PhixFlow adds a field and label for each attribute. By default, the label is the attribute's name. However, for an attribute from a related table, the Display Name will be shown and not the foreign key value.

For example:

For information about primary and foreign keys and the Display Name option; see Entity Relationship Diagrams.

If a form field or dynamic text field exists on a screen, it will link to an attribute in the data backing the screen by name, however you can also right-click on these components and select Change Backing Attribute to link it to any available attribute.