Business Application Modeling error messages

The file cannot be loaded; depending on the error, the message can change:

• Unknown node: an unknown node is present in the settings file
• Cannot register node: a node cannot be added to the file format (it's invalid or already present)
• Empty extension: a required file extension is empty.

Check file path, format and permissions.

Check file path, format and permissions.

Check template directory path.

The setting.agconf template file format is incorrect. Validate it using the XML schema (or open it in Code Editor) and fix the errors.

The settings.agconf file version attribute is not present.

Add a version attribute corresponding to the product.

Modify setting.agconf to match version 2 XML schema.

%1 BLOCK(S) or POINT(S) end tag is(are) missing.

Fix the BLOCK / POINT..

Incorrect end BLOCK or POINT tag type.

Fix the BLOCK / POINT.

End BLOCK or POINT tag does not correspond to an open tag.

Fix the BLOCK / POINT.

Rename the BLOCK / POINT.

Rename the BLOCK / POINT.

Preprocessor message that a BLOCK / POINT has been renamed:

%1 = BLOCK or POINT

%2 = old BLOCK / POINT name

%3 = new BLOCK / POINT name

%1 = BLOCK or POINT

%2 = BLOCK / POINT name

Add a BLOCK / POINT in the templates or remove your code.

Modify the build rule to use the new commands.

%1 = BLOCK or POINT

%2 = BLOCK / POINT name

An unknown property has been set in the settings file. Remove the property or change its name.

Check the rights on the generated source file.

Check the rights on the generated source file.

Check the rights on the generated source file.

Check the rights on the code file.

Check the rights on the code file or check that the code file contains valid XML content.

The command $(blockpoint) contains an unknown argument in the build rule. Check the argument %1 of $(blockpoint) command in the build rule.

The Application Generator build rule requires the -depth argument in the $generate command. Add the -depth argument to the $(generate) command in Application Generator build rules.  

Command or tclsh or $(agcomp) contains an unknown argument in the build rule. Check the argument %1 of $(generate) or tclsh or $(agcomp) command in the build rules.

The command $(blockpoint) contains an -endComment argument without -startComment argument in the build rules. Remove the -endComment argument or add a -startComment argument in the build rule.  

The file contents cannot be decoded with the codec, the encoding specified in the environment does not correspond to the file and it cannot be read. Change the encoding so that it supports all the file characters.

The file contents cannot be encoded with the codec, the encoding specified in the environment does not correspond to the file and it cannot be written to. Change the encoding so that it supports all the file characters.

There is no default text codec for the specified encoding. Use another alias for this encoding, update encodingMap.xml, or add a new POSIX charmap.

The BLOCK/POINT start tag has a wrong syntax. Restore the right syntax.

Some characters have changed outside the topmost block, which is not supported. Insert a new toplevel block around the code you want to modify and regenerate the code.

The $(BlockPoint) command is used with multiple generated files, the -code argument is mandatory. Add the -code argument.

The $(BlockPoint) command is used without generated files arguments. Add the generated files list.

Some file managed by the .code were not updated by the $(BlockPoint) command, the .code is not completely up to date. Add the missing files to the command line in the build rule or remove the old file from the .code if they are no longer useful.

The current version of Genero Studio does not support this version of .code file.

Upgrade Genero Studio.

The .code file encoding is not the same as the build encoding, the resulting files may be incorrect.

Change the build encoding (the LANG variable for example) to match the .code file encoding or rewrite the .code file with the current encoding.

The code file id does not match the source file id, thus a resulting conflict file. You must merge the differences manually. This may occur after updating from the SVN repository.

Merge the .conflict file and the source file, then delete the .conflict file.

The code file id does not match the source file id, thus a resulting conflict file which cannot be written to the disk.

Check the directory permissions.

In the settings.agconf file, an attribute has been defined where it is not expected.

If the attribute is not required, remove it. If the attribute is required but has an error (a spelling error, for example), fix the error.

Some Business Application deprecated feature has been used.

Refer to the migration notes in the manual to update the project. In this example, modify the settings.agcong to add the depth, and edit the build rules to remove the depth.

The Business Application template directory setting is set incorrect.

Business Application build command $(BlockPoint) failed, there are inconsistencies between the source files and the code files. This error should not happen during normal operations, but may appear in case of errors during the process of migration between different versions.

If you receive this message, contact support for help during the migration.

The Open Mode property value is empty. The available values are: DISPLAY, MODIFY, ADD, SEARCH and EMPTY. Check settings.agconf and ensure that the initialValue attribute of the <DynamicProperty> node having name = "openMode" contains one of the available values.

The Action property is mandatory when a relation is defined between modules (4fdm to 4fdm) or between module and zoom (4fdm to 4fdz) and the relation type=Relation. Check that the Type property of the relation is Relation. Check that the Action property of the relation is not empty.

If the Report File property is empty, the default layout (ASCII mode) will be used when a relation is defined between a module and a report (4fdm to 4rd) and the relation type=ReportRelation. This is a warning message. Check that the Type property of the relation is ReportRelation. Check that the Report File property of the relation is not empty.

The type of relation is not valid between entities: module (4fdm), program (4prg), zoom (4fdz), report (4rd). Check the Type property of the supported relation and ensure that the relation is supported.

Check the entity relations.

Check the entity relations.

Absolute paths are not recommended because the project will not be portable. Use a relative path. Be sure that your Genero environment variables are correctly set to search for your resource files.

All fields making up the unique key of a record must be fields of the master table of the record. Uncheck the Unique Key property of fields which are not of the master table of the record.

The joins between a pair of tables must have the same join operator. Check that there are not multiple join operators for the same pair of tables.

The field that is updated via an ascending lookup is mandatory in the master table of the record. Add the field to the master table of the record. Currently, the field is only defined in the Query clause of the record. If you don't want to see this field on your form, use the phantom widget. Or, delete the lookup property of the field which triggers the ascending lookup.

When there are several records in a managed Form, only one can be the master. This error occurs when at least one record is not linked by a relation. In the Records view, check that all records are linked by a relation.

A relation must have the same number of primary fields and foreign fields. Modify the relation fields so that a primary field corresponds to each foreign field.

Rename your action to a name other than zoom.

Several relations use the same combination of Action/Source Record property values.

$1 - Number of relations having the same combination of Action/Source Record.

$2 - Action name.

$3 - List of record names.

Rename Action or change the Source Record to have a unique couple.

The filename contains invalid characters. Identifiers must confirm to these rules:

• It must include at least one character, without any limitation in size.
• Only ASCII letters, digits, and underscore ( _ ) symbols are valid.
• No blanks, hyphens, and other non-alphanumeric characters.
• The initial character must be a letter or an underscore.
• It is recommended to always write identifiers in lower case.

Rename the file to a valid file name. If the file was generated, renaming the object may not be enough; you will have to rename the file itself to match the new object name in Project Manager.

Make all initializer names unique.

Set the initializer or the items property of the ComboBox.

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.

Duplicated joins are forbidden in the query.

Remove the duplicated joins.

The build process of the file ($1) has been aborted because the intermediate XML file has a version ($2) which mismatches the template version ($3).

Use a valid template set defined in Application Generator Preferences. Verify build rules for the appropriate file type.

In the Business Application diagram, the openMode or defaultMode property defined on a relation between a CRUD Form and a Zoom Form is not supported. Only DISPLAY and SEARCH values are currently supported on a Zoom. Change the openMode or defaultMode property to a supported value.

The $1 property is missing in settings.agconf.

The build process has been aborted because the $1 dynamicProperty is missing in the settings.agconf configuration file.

Check settings.agconf and confirm:

A primary key needs to be defined for the given table in order to have its CRUD functions generated when compiling the database schema.

On incoming relations of a CRUD Form or Zoom Form, the openMode and defaultMode property must follow the same rules as those forms.

To fix the error, change the openMode or defaultMode property value or change the functionality of the record.

An XPath cannot be resolved. Check the XML intermediate file.

Change the number of source fields defined on the relation.

The destination fields defined on a Zoom relation will not appear in the generated 4gl code.

A database schema field of datatype SERIAL can only be handled by using the seqreg table. This table contains a list of table names and values, a value is the last SERIAL created for a given table name. In case the couple (table name, last value) does not exist, a new record will be created and the SERIAL value will start at 1.

Only one SERIAL field can be managed per database table. This is inherent to the seqreg table.

Add a Business Application Diagram to the project.

All fields making up the unique key of a record must be either a database primary key or secondary key of the master table (unique constraint).

Change the unique key property of fields which are not a database primary key or secondary key of the master table or update the 4dbx schema.

Select a table in the master table property.

In the Business Application diagram, when a relation is defined between items, the Source Field and the Destination Field must exist in the Records view.

Check the Source Field and/or Destination Field property of the relation or open the appropriate item and add the missing fields.

In the Business Application diagram, a relation between Forms must have the same number of fields in the Source Field and Destination Field.

Check  the Source Field and/or Destination Field property of the relation.

The property Service Name of a WebService item must have a value in the Business Application Diagram.

Set the Service Name property value.

Set the Namespace property value.

Any web service registered to the same Web Service Server must have an unique name.

Ensure that the property Name of a web service is unique.

In the Business Application Diagram, when a relation is defined between items, the Action property can not be a reserved action name. The list of reserved action names is defined in the action defaults file (dbapp.4ad).

Set the value of the Action property to a non-reserved action name.

An unexpected internal error occurred during code generation. Contact your local Four Js support center.

The LANG environment variable is set, but the encoding part is either invalid (change the value of the LANG environment variable) or not present in the supported encoding array (add an entry in encoding.tcl).

Choose fields from the same record.

In the Business Application diagram, when a relation is defined between items, the Record Source must exist in the Records view. Check the Source Record property of the relation or open the source entity and add the missing record.

The Source Record property is missing in the Business Application diagram. When a relation is defined between items, if the Row Bound property is checked on an outgoing relation, the Record Source must be defined if there is more than one record in the form. It is implicit if there is only one record.

Check the Source Record property of the relation or uncheck the Row Bound property.

Some functionality is not supported by the template. For example canAdd, canModify, and canSearch are not supported for tables.

Uncheck the functionality.

Remove the ambiguity and choose a record.

Uncheck the Row Bound property or choose the table container in the form.

The position Source Field is required when the destination of the relation is a zoom.

Some containers such Tree and ScrollGrid are not supported on mobile devices. Change container to a supported container.

This message is a warning, not an error. It simply tells you that all functionality is disabled for the record in question. Verify that having no functionality selected for the record is intentional.

Ensure the data type of the field is compatible with the aggregation function:

• AVG and SUM can only be performed on Numeric fields.
• COUNT and DISTINCT COUNT cannot be performed on a Byte field.
• MAX and MIN cannot be performed on a Byte or Boolean field.

The Java file argument of the 'schemagen' tool is missing. This error can occur on a build of a ReportData file(.4rdj) with Java.

Ensure that the generated Java file exists.

An error occurred when the external tool used to create the schema file was executing. This error can occur on a build of a ReportData file(.4rdj) with Java.

In the Business Application diagram, a warning is raised when a property is unused in code generation.

Reset the unused property to the default value to remove this warning.

If the databaseName property is not defined on the first form defined of the outgoing relation of a program, then that database connection is not generated in the program.

In the Business Application diagram, a program has an outgoing relationship to an unimplemented form.

Implement the form.