> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/editable/formula-and-functions.md). # Formula and Functions EDITable features an Excel-like formula engine that supports over 50 functions, including logical, boolean, date, math, and others. The formula editor is intuitive and user-friendly and offers dynamic help suggestions regarding syntax and examples. It includes features like auto-complete and multi-line support to better assist users in creating and troubleshooting formulas. :heavy\_check\_mark:Type the formula in the formula editor while setting up the default values, derived from the data. :heavy\_check\_mark: Use formulas while inserting a formula column. :heavy\_check\_mark: Enter formulas and operators directly into the table's cells to perform calculations. :heavy\_check\_mark: Copy and extend the formulas to the cells below, similar to Excel's 'fill' feature.\ \ Please refer to the sections below for a detailed list of the formulas, functions, and operators available for calculations. * Conditional Statements * Logical Functions * Math Functions * Text Formatting Functions * Date functions * Other Operators --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.inforiver.com/editable/formula-and-functions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.