Field Service Sizes
Some field service operations may need to track the size of a field service location and its orders.
Examples of sizes might be: - Area measure of a location - Count of service or maintenance items at a location
Once established, sizes can be useful for route capacity planning, time estimation for orders, or for planning stock and inventory moves.
This module allows you to establish sizes for your field service orders. Multiple sizes can be configured and established for a location. Order size will be updated based on its location and order type.
Table of contents
Configuration
To configure field service sizes, go to Configuration > Sizes.
Set the size name, type of orders to which the size will apply, and unit of measure for the size. If this size is the default size to be used for orders of the designated type, select the option for ‘Is Order Size’.
Usage
## Enter sizes for field service locations. Go to Master Data > Locations
Select or create a location.
Go to the Sizes tab.
Select a Size. Enter the value for the size.
## Use Order Sizes
Select or create a field service order.
Set a location on the order.
Set a type on the order.
The size value will update to the location’s size value of the order type’s default size.
Known issues / Roadmap
The roadmap of the Field Service application is documented on Github.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Brian McMaster <brian@mcmpest.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-fieldservice-size 12.0.0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo12_addon_fieldservice_size-12.0.0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo12_addon_fieldservice_size-12.0.0.1.1-py3-none-any.whl
| Download URL | odoo12_addon_fieldservice_size-12.0.0.1.1-py3-none-any.whl |
|---|---|
| Size | 30.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a9614a5b3364e7c825f45f543e2854d046fe9184ca8497be961e734d34b8368
|
|
BLAKE2b-256 checksum How to use checksums |
f7a102eae026afd24749a3c80c47bb81fc271f10d8c8ffe690ac68c6f1231e20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-fieldservice-size 12.0.0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
