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
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
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
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
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.
