Product Dynamic Codes v.13
The tool to flexibly and automatically update product internal references
Advanced rules to construct product reference
Code positions for certain products might be empty: e.g. for services there is no sense to have a code part of the attribute 'material'.
Each position has rules to generate a code value. For example, for products made of aluminum it is '-AL', for products with material steel it is '-ST'. In order a code part is calculated for this product, there should be at least a single rule this product satisfies.
Screenshots
Product reference is updated according to coding rules
Have as many code positions (parts) as required
Flexibly configure rules to combine a product internal reference
Static and dynamic code parts
How dynamic code parts work
- Use fields of a product variant and product templates
- Apply any field of the types: char, integer, float, date and date with time, selection, and many2one.
- Rely upon any standard or custom fields (e.g. manufacturer or manufacture date)
- In case of many2one field (e.g. a related product category) you should select its field (for example, category name or category custom code)
- Use not the whole field value, but its part. For instance, apply first 2 letters (0-1) of a category name or only month of a manufacture date (5-7). Leave '0' in both start and end to retrieve the whole field value
Screenshots
Use product field values to generate auto references
Apply static code parts based on products filtering
Code rule with filtering by categories
Product automatic reference (example)
Automatic generation of codes
For certain product templates and variants you can switch the auto update off. If you mark items as 'Manual reference': their codes will be not generated by rules. References become editable for such products and should be updated by users. Take into account that if during creation (e.g. import) you introduce a default code, related product would be automatically set up as one with manual reference.
When product references are updated
Codes are updated in the following cases:
- When a product is created or updated
- Regularly by the cron job for all products (have a look a the tab 'Configuration', the section 'Scheduled jobs')
- Manually when you push the button on a product form
- Manually for all products when you push the button on the configuration page
Why the logic is so complex? To avoid slowdowns. The point is that codes rules are advanced and there is no way to define recalculation triggers. Generating codes on fly would result in low performance. That is why to make sure codes are generated, Odoo regularly look over all products.
Screenshots
Exclude products from reference automatic updates
Coding relies upon standard Odoo tools
Product coding is global: rules are applied to each company in the same way. Simultaneously, you can restrict products in rules by using filters by company.
The right to define product coding rules belongs only to Odoo administrators.
Configuration and Installation Tips for Product Dynamic Codes Odoo v.13
Scheduled jobs
- Turn on debug mode
- Go to technical settings > Automation > Scheduled jobs
- Find the job 'Construct Dynamic Codes'
Frequently Asked Questions about Product Dynamic Codes Odoo v.13
According to the current Odoo Apps Store policies:
- every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
- starting from version 13.0, every module version should be purchased separately.
- disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.
Take into account that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.
The easiest approach is to use the Odoo store built-in workflow:
1. Open the module's page and click the button Deploy on odoo.sh
2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project
3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.
These steps will install the app for your project production branch. If you want to deploy the apps for other branches or update the module, you should undertake the following actions:
1. Upload the source code for the app from the Odoo store
2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions
3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.
Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;
Re-start the Odoo server;
Turn on the developer mode (technical settings);
Update the apps' list (the apps' menu);
Find the app and push the button 'Install';
Follow the guidelines on the app's page if those exist.
Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.
A red/orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.
So, first of all, please check deployed database features. Does everything work correctly?
If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).
No, we distribute the tools only through the official Odoo apps store
Regretfully, we do not have a technical possibility to provide individual prices.
No, third party apps can not be used on Odoo Online.
Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.
The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.
Bug reporting
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).
Public features requests and module ideas (free development)
We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.
Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
The technical core to synchronize your cloud storage solution with Odoo
The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS
298€
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
The tool to automatically synchronize Odoo attachments with Google Drive files in both ways
The tool for time-based service management from booking appointment to sale and reviews
398€
The tool to make inventory data essential and comfortable for elaboration
The tool to calculate stock demand trends and make prediction for future demand statistically. Stock Forecast
98€
The tool to restrict users' access to stocks, locations and warehouse operations
28€