> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/epoch-datetime-function.md).

# Epoch Date/Time Function

## Description

Epoch -- the Unix epoch (or Unix time or POSIX time or Unix timestamp) -- is defined as the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds (ISO 8601: 1970-01-01T00:00:00Z). Many software systems use epoch as the storage format for a date/timestamp. Since epoch stamp is based on Coordinated Universal Time (UTC) it is affected both by Daylight Saving Time (DST) and time zone changes.

Several LogicNets parts support the epoch format as well as the standard LogicNets time format of YYYYMMDD.HHMMSS. The standard LogicNets date/time storage format does not indicate time zones or DST. Therefore, we recommend storing timestamps in UTC/GMT time-zone or as epoch.

Some parts support date/time conversion (e.g. stamp stored as epoch is displayed in a human-readable format). In these cases, you must provide the time zone and DST. Note: LogicNets currently supports two time zones: GMT/UTC and server/local (this is the time zone of the server on which LogicNets is running).

The following LogicNets parts work with date/time stamps:

| Part                      | Description                                                                                                       | Input Formats            | Output Formats              |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------ | --------------------------- |
| create\_epoch\_date\_time | This converts between YYYYMMDD.HHMMSS and epoch formats.                                                          | Epoch \| LN Format       | Epoch \| LN Format          |
| set\_current\_date\_time  | This retrieves the current date/time stamp.                                                                       | -                        | Epoch \| LN Format          |
| date\_calculation         | This adds/subtracts days/hours/minutes/seconds from the provided stamp.                                           | LN Format                | LN Format                   |
| format\_variable          | This formats and displays a value in a human-readable format that you can set when the data type is "date\_time". | YYYYMMDD.HHMMSS \| Epoch | LN Format \| Display Format |
| date\_difference          | This calculates the difference between two different date/time stamps.                                            | YYYYMMDD.HHMMSS \| Epoch | Epoch \| YYYYMMDD.HHMMSS    |
| db\_grid3                 | This displays the contents of a data table.                                                                       | Epoch \| LN Format       | LN Format \| Display Format |


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/epoch-datetime-function.md?ask=<question>&goal=<user_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.
