Edition: Futurama Website/Futurama Export/Futurama Webservice

Module: Futurama Editor

User: Developer


- Evaluating objects



During the development of an application errors will occur frequently, most often when creating Formulas and when working with sources outside Futurama like Databases, Vision etc.. Unlike Validation messages, which can be considered more as warnings, errors need to be resolved. In this page it is explained how to troubleshoot Errors. The Errors Window is explained as well as a number of settings in the Futurama Editor which are relevant for troubleshooting. A number of frequently occuring Error messages will be discussed here as well. The mechanics of logging errors during runtime to a file or the trace is not covered in this page. See Logging errors for more information on this.

Errors Window

The Errors window shows errors the moment they turn up. Of every Error the following information is provided:

  • Type: the type of error e.g. a system.exception
  • Time: the timestamp on which the error occured
  • Message: The message stating what went wrong

When hovering over an error a tooltip will appear containing the same information.

Error settings

A number of settings are available concerning errors and warnings. These are available in the menu-item Tools | Settings:

  • ActivateErrorBoxOnError: Possible values are True/False. If set to True errors will appear in the Error box the moment they occur and the focus will shift to the Error Window as well.
  • DisplayStackTrace: Possible values are True/False. If set to True in addition to the Error message also the stacktrace will be given. This extra information can be helpfull when solving the error. If set to False only the Error message will appear.
  • WarnForInvalidFormula: Possible values are True/False. If set to True a warning will occur when evaluating an invalid Formula.
  • WarnForMovePublicObjects: Possible values are True/False. If set to True a warning will appear when an object, which has the property IsPublic set to True, is moved. The reason for this is that objects that are designated as Public can be referred to by objects in other documents. Moving these objects therefore takes extra caution because the objects that refer to them become invalid when the object is moved.

Common error messages

The following list contains a number of frequently occuring error messages. Every message will be explained briefly.

  • Error executing formula: This message applies to Formulas. It indicates that a Formula cannot be evaluated because it is not properly defined. The reason(s) for this can be numerous e.g. a Formula that refers to itself or when trying to add two tables with different dimensions. The stacktrace often gives enough information about the cause of the error.
  • Error connecting to DB Connectstring = : This message applies to DatabaseViews. It indicates that an error occured when trying to access the database. The reason can be that the connectionstring is erroneous, that the database itself can't be found or that the user does not have the proper rights to access the database.
  • Error opening query : This message applies to DatabaseViews and is most often accompanied by the error above. The reason is often that the database can't be accessed or that the query that is to be executed is erroneous.

Related Topics

- Evaluating objects: Explanation of the Result Window, Validate Window and Errors Window.

- Logging errors: Explanation how Errors can be logged.


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2014-02-28