Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »


Overview

Here you can find some commonly asked questions and problems, and their solutions.

Re-used Actionflow Working Intermittently 

Problem

An Actionflow is reused on different components, e.g. a grid and a card container. The Actionflow works as expected on one component but not the other.

 Solution

Solution

Check that the fields on the component where it is not working are backed by a table attribute.


Backed Form Fields Not Populating 

Problem

Form fields on a component are not populating despite having backing attributes. 

 Solution

Solution

If the component is backed by a View then PhixFlow returns the data for the View, rather than the backing attribute form fields.
To resolve this, remove the View, found in the Advanced section of the Card Component Properties, or add the required fields to the View.

"Failed to convert" Error Message After Running Actionflow

Problem

The following error message shows when running an Actionflow:

Failed to convert value of type 'java.lang.String' to required type 'com.accipia.centerview.web.parameters.ActionRunParameters'; nested exception is java.lang.IllegalArgumentException


 Solution

Solution

This is caused by a Type mismatch (i.e. integer, decimal, string, etc.) between a field and its backing attribute. For example, you may have a dynamic text field set to a Type of Integer, but backed by an attribute with the Type of String.

Database Exporter Not Recognising Import Attributes in Tables 

Problem

A push pipe triggers a database exporter that reads data from a pull pipe. The database exporter has a Statement Expression containing an attribute located in a pull pipe table. When the database is exported, an error message shows: "Failed to get value for record while taking a stripe for attribute. Could not find attribute".

 Solution

Solution

The error message shows because the first record that the exporter receives is from the push pipe, which doesn't have the referenced attributes. The data received from the pull pipe is then correctly exported. 


Illegal Group Reference

Problem

Failing to push records through an HTTP Collector in an Analysis model. The error in the System Console logs contains "Illegal Group Reference".

This is typically an issue with the escaping of backslashes in an expression.  

 Solution

Solution

Check the Application's Properties → Advanced Section → Backslashes must be escaped in expressions.

There is a change in PhixFlow version 9.0.0 which affected escaped backslashes in expressions. This option maintains backwards compatibility. By default this will be ticked for applications created before 9.0.0, and unticked for later applications.

If you need to escape a backslash for an HTTP Collector we recommend:

  1. Create a new Package
  2. Associate it to your application
  3. Move the HTTP Collector to the new Package
  4.  Enable the option for Properties → Advanced Section → Backslashes must be escaped in expressions.
  5. You will now be able to escape backslashes in your HTTP Collector as required.


PhixFlow V8.3 Grid Styling

Problem

Upgrading from PhixFlow version 8.3 to version 11 has changed the styling of some grids and the white grid lines separating each attribute column are no longer visible.

 Solution

Solution

In order to preserve the v8.3 grid styling, set the following Styles:

Grid Row Style

  • Height: 18px
  • BorderRight: 1px solid #d3d3d3
    • In v10, build < 38591, this property can be set in the Grid Column Style

Grid Alternate Row Style

  • Background Colour: #e6e6e6

Row Selection Style

  • Background Colour: #07e51c

Grid Row Hover Style

  • Background Colour: #22FF37



  • No labels