mirror of
https://github.com/inventree/InvenTree.git
synced 2025-04-28 19:46:46 +00:00
ce617b7792
* Remove hard-coded credits from docs - Extract *actual* package credits - Auto-build into docs * Include URLs when generating python license data * Update readthedocs process * Better URL extraction * Adjust build process for RTD * Spelling fixes * Install node and yarn * Command fix * Improved library sorting * Improved error message * Remove credits.md * Cleanup * Further cleanup * Tweak playwright test * Handle uncaught exception in fetchIcons * Fix for CORS settings in playwright testing * Enhance login check * Fix for barcode test --------- Co-authored-by: Matthias Mair <code@mjmair.com>
54 lines
3.0 KiB
Markdown
54 lines
3.0 KiB
Markdown
---
|
|
title: Reference Patterns
|
|
---
|
|
|
|
## Reference Patterns
|
|
|
|
InvenTree contains a number of data models which require a *unique* reference field (such as [Purchase Orders](../order/purchase_order.md)). In addition to being *unique* these reference values must conform to a specific *pattern* (which can be defined by the user). Defined reference patterns also make it simple for the user to control how references are generated.
|
|
|
|
### Default Patterns
|
|
|
|
Out of the box, InvenTree defines a standard "pattern" for each type of reference (which can be edited via the InvenTree [settings interface](./global.md)).
|
|
|
|
| Model Type | Default Pattern | Example Output |
|
|
| --- | --- | --- |
|
|
| Purchase Order | `{% raw %}PO-{ref:04d}{% endraw %}` | PO-0001 |
|
|
| Sales Order | `{% raw %}SO-{ref:04d}{% endraw %}` | SO-0123 |
|
|
| Build Order | `{% raw %}BO-{ref:04d}{% endraw %}` | BO-1234 |
|
|
| Return Order | `{% raw %} RMA-{ref:04d}{% endraw %}` | RMA-0987 |
|
|
|
|
### Pattern Requirements
|
|
|
|
Patterns can contain a mixture of literal strings, named variable blocks, and wildcard characters:
|
|
|
|
- The pattern **must** contain a single `{% raw %}{ref}{% endraw %}` variable - this is the required sequential part of the pattern
|
|
- A `?` (question mark) character is treated as a wildcard which will match any character
|
|
- A `#` (hash) character is treated as a wildcard which will match any digit `0-9`
|
|
- Any other characters will be matched literally
|
|
|
|
### Variables
|
|
|
|
When building a reference, the following variables are available for use:
|
|
|
|
| Variable | Description |
|
|
| --- | --- |
|
|
| `{% raw %}{ref}{% endraw %}` | Incrementing portion of the reference (**required*). Determines which part of the reference field auto-increments |
|
|
| `{% raw %}{date}{% endraw %}` | The current date / time. This is a [Python datetime object](https://docs.python.org/3/library/datetime.html#datetime.datetime.now) |
|
|
| `{% raw %}{?:default}{% endraw %}` | A wildcard *with default*. Any character(s) will be accepted in this position, but the reference pattern suggests the character(s) specified. |
|
|
|
|
The reference field pattern uses <a href="https://www.w3schools.com/python/ref_string_format.asp">Python string formatting</a> for value substitution.
|
|
|
|
!!! tip "Date Formatting"
|
|
The `{% raw %}{date}{% endraw %}` variable can be formatted using the [Python Format Codes](https://docs.python.org/3/library/datetime.html#strftime-strptime-behavior).
|
|
|
|
#### Substitution Examples
|
|
|
|
Some examples below demonstrate how the variable substitution can be implemented:
|
|
|
|
| Pattern | Description | Example Output(s) |
|
|
| --- | --- | --- |
|
|
| `{% raw %}PO-{ref}{% endraw %}` | Render the *reference* variable without any custom formatting | PO-123 |
|
|
| `{% raw %}PO-{ref:05d}{% endraw %}` | Render the *reference* variable as a 5-digit decimal number | PO-00123 |
|
|
| `{% raw %}PO-{ref:05d}-{?:A}{% endraw %}` | *Require* a wildcard suffix with default suggested suffix `"A"`. | PO-00123-A <br> PO-00123-B |
|
|
| `{% raw %}PO-{ref:05d}-{date:%Y-%m-%d}{% endraw %}` | Render the *date* variable in ISO format | PO-00123-2023-01-17 |
|