> 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/formula-syntax/time-intelligence-functions/valueat.md). # VALUEAT The VALUEAT function returns the value of a measure for a specified date or a date shift relative to the current column. ## Syntax ```javascript VALUEAT([measure], ) ``` ## Arguments measure – The measure for which data has to be fetched. Required. offset interval - The preset format model, like month("M"), quarter("Q) or year("Y"). Required. ## Return value The measure value at a specific point in time. ## Example ``` VALUEAT([Sales], "-1M") //Returns the sales measure from the preceding month VALUEAT([Sales], "1Q") //Returns the sales measure from the next quarter ``` Let's look at a monthly sales report. The VALUEAT function can be applied to return the value of the sales measure for a particular month(s) preceding or after the current month. This is useful in evaluating the financial performance relative to other periods.

Fetching the measure value for the previous month

Similarly, we can fetch the sales value for the next quarter as shown in this example.

Fetching the measure value for the next quarter

--- # 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/formula-syntax/time-intelligence-functions/valueat.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.