Using the flex query view

Use the flex query view tool to create queries on style data. You can build queries using available fields on each tab of the Style module, then display the results in a single view that you also define.

You can use Style Overview extended fields in the column chooser, advanced filters, and report XML. All five extended field types are supported: text, generic lookup, number, date, and checkbox.

The flex query view displays the label of the extended field and not its name.

A validation is in place in case an extended field is already part of a flex query view and you updated its label from the Extended Field library. This validation is triggered when you open or refresh the flex query view record. You must remove the old extended field from the grid and/or in advanced filters and add them again using the updated extended field label. The query will not return data if you fail to do this.

The styles that are included in the result set depend on the data hierarchy. You can only view items that you have access to.

See Hierarchy.

You can also generate an XML file based on your query view, then use the XML file as content source input when creating a report layout using a Word document with Infor Document Management extension. You can create a report template and import this Word document and the XML file. Using the template, you can generate a report in flex query view or style list.

Based on the result set, you can generate reports and export to Excel.

Note: 
  • The column field labels in the flex query view do not show the translated text. If you set your browser language to any of the supported languages aside from English, the English text is displayed even if label translations are available.
  • If text translations are available, they are displayed in the flex query view grid cells. For example, if your browser language is set to French and a French translation for Style Status value is available, the French translation is shown in the flex query view grid.

    See Translating input data.

  • All non-alphanumeric characters in extended field labels are converted to an underscore in the generated XML file.
  • Flex query views cannot retrieved data if an extended field has a dot on its label. You must replace dots with another character.