Troubleshooting Mobile Form Expressions Checklist

Use this checklist to diagnose configuration problems in Mobile form expressions.

Check

Verify

If the Check Fails

Element and Property Names

Confirm that each referenced element and property name is spelled correctly and uses the correct letter case.

Correct the referenced element name or property name, including letter case.

JavaScript Identifiers and URIs

Confirm that each element name, import ID, and custom property name is a valid JavaScript identifier.

Confirm that each URI is unique. If an expression references a URI, confirm that the URI is also a valid JavaScript identifier.

Correct the invalid identifier or URI and update the related expression reference.

Expression References

Confirm that each expression references only available element properties, imports, and functions.

Correct or remove unavailable references.

Result Data Type

Confirm that the expression result has the data type expected by the target property.

Correct the expression result or the target property data type.

Table References

Confirm that table references are within the supported scope.

Confirm the supported scope for table references.

Error Logging

Set the FSM Configuration log option to true. Determine whether the log reports a parse error or a runtime error.

Correct the reported parse or runtime error.

Circular Dependencies

Confirm that expressions don't create update loops through reciprocal property dependencies.

Use a single shared calculation where possible. If a reciprocal dependency is required, make sure the calculation reaches a stable value and has an explicit exit condition.

Imported Files

Use a new import ID after you update an imported file.

Change the import ID in the FSM Configuration.

Related Topics

General Notices