Fixing a BigQuant Expression Type Error by Enabling the Position Formula

Summary

A BigQuant user reports an error stating that an expression argument was expected to be a string but instead was null. The reported fix is to enable the position formula option in the position allocation module. This identifies a configuration setting that can resolve the error when the underlying issue is an unset position formula, even though the error message itself may not point clearly to that setting.

The post is a single troubleshooting report rather than a general diagnosis. It does not explain why the unchecked option passes a null value, specify the affected platform version, or document other causes that could produce the same error. Traders encountering this message can use the setting as a focused configuration check, while recognizing that the report does not establish it as a universal fix.

Key ideas

• A BigQuant user encountered a type error because an expression value was null instead of a string.
• Enabling the position formula option in the position allocation module resolved the reported case.
• The error message did not directly identify the relevant configuration setting.
• The post does not establish whether this fix applies to other causes or platform versions.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.