Business Records error messages

An error occurred loading the file.

Check the file name and permissions .

XML file content is invalid.

Select the correct file or correct the XML.

A referenced element is not found in the Business Application diagram.

Select the correct file.

Check the property syntax in the documentation and correct any errors.

Conflicted item.

The Business Application diagram and Business Record unique id do not match.

Open the 4ba file and resolve the conflict.

The document must contain at least one record that is master.

Create a record.

At least one field must be declared the unique key in a record.

Set a unique key.

Change the record to active, or remove the relation.

This relation has no field definition.

Add foreign/primary (or source/destination) fields.

In one form, a database table column can be referred only once. Table aliases should be used to attach more than one field to a database.

• Select one of the wrong Formfields and change the fieldType attribute from table_column to table_alias.
• Select one of the wrong Formfields and change fieldType attribute to non_database.

Set the master table property.

A database table is used in the record, but there is no join for it in the query.

Add a join for the table in the record query.

A database is required for the business records.

Set the database name property to an existing database.

Modify the relation fields so that a primary field corresponds to each foreign field.

Check the query fields so that a left field corresponds to each right field.

The type of a foreign key doesn't match the corresponding primary key's type.

Check the relation, change the field types, or fix the primary / foreign key.

The relation refers a field that is missing in the record.

Check the schema being referenced.

The document uses a database table that is not present in the schema.

Update the schema, or change the field using the table.

The document uses a database column that is not present in the schema.

Update the schema or change the field using the table.column.

Set the database property to an existing schema or remove the field.

The same table alias is associated with two columns in the form.

• Change one table alias name.
• Change either the table or column name.  

The same alias is used for different tables.

Rename the alias so that it refers to the same database table.

Alias Lookup field is ignored on %1 as it is the master table of the record.

A lookup field is dedicated to foreign field update in the master table; do not set it on a master table column.

Remove the lookup property value or update the field database settings.

Duplicate name used in the document.

Rename the element so that the name is unique.

The qual1 or qual2 set for the INTERVAL sqlType is not valid. It should belong to the INTERVAL classes (i.e., YEAR-MONTH or DAY-TIME)

Change either qual1 or qual2 to fit the respective class range or change the sqlType property from INTERVAL to another sqlType.

The qual1 value should be greater than the qual2 value, when the sqlType is either DATETIME or INTERVAL.

Ensure qual1 is greater than qual2 or change the sqlType property from INTERVAL to another sqlType.

Some query properties (join, order, additional tables or where) are defined without a database schema attached.

Clear the query properties or attach a database schema to document.

A table is referenced in a query property (join or order), but is not referenced in any record's field or additional tables.

• Remove the join or order that references this table.
• Add a field referencing a column from this table to the record.
• Add the table to the 'additional properties' property.
• In the join or order, change the table to another one that is present in the record.

The value is not compatible with dataType set. This error occurs when defaultValue and include property value is incompatible with dataType property.

Change defaultValue/include, enter a value compatible to dataType format.   

Invalid join between %1 and %2.

• Remove the join

• Change the operator

• Change the join table(s)

There is no join between table %1 and master table.

• Add the missing join for the %1 table
• Remove the table %1  

Invalid initializer.

Change the initializer to respect the format. 

Invalid source %1 for initializer %2.

Change the initializer to respect the format.

Initializer property %1 is missing.

Change the property name in the initializer.

The initializer cannot be resolved, the database element is not found, or the property is missing.

Change the initializer to point to a valid element.

The document contains a dynamic property which is not present in the Application Generator template directory settings (orphan property). These orphan properties won’t be taken into account during compilation. The Application Generator settings dynamic properties should match the document ones, otherwise this error is generated.

• Add the orphan properties to the settings.agconf file.
• Remove the properties from the document using Tools >> Specific setup >> Clean orphan properties.

Orphan property group %1.

The document contains a dynamic property group which is not present in the Application Generator template directory settings (orphan property). The Application Generator settings dynamic properties should match the document ones, otherwise this error is generated.

• Add the orphan property groups to the settings.agconf file.
• Remove the properties from the document using Tools >> Specific setup >> Clean orphan properties.

File type not defined in Application Generator settings.

Add the item type definition to the settings.agconf.

The property initializer uses the database schema but the file doesn’t have a schema.

• Set the database.
• Set the property value so that the initializer is not resolved.
• Remove the initializer.

The unique key field value contains one field which is not in the record.

• Remove the field from the unique key.
• Add the field to the record.

Inactive table %1 in the database schema.

The database table active flag is set to false, the table is inactive and cannot be used for code generation.

Make the table active or do not use it.