6. Vreports malfunctions creating reports on "Transactional" modules with respect services/products
Last updated
Last updated
When transactional modules (QUO/INV/PO/SO) are selected in the primary module and the products/services modules are selected in the second module. Vreport output will show distorted data
This is likely due to the relationship structure. The "transactional" modules (QUO/INV/PO/SO) have special relationships with services/products.
The way you can look at it:
Primary Module: Products
Secondary Module: Purchase Orders
It works, because you can see related PO's to the Product:
However, if you look at the Purchase Order module, you do not see the opposite relationship:
When creating reports for any module, if the data on the report is not complete/correct (or it does not work at all) - it is recommended to switch primary & secondary module to see if other variation works as expected.
Extension | Vreports & Dashboards |
---|---|
Description
Vreports malfunctions creating reports on "transactional" modules with respect to services/products
Created by
Salman (November 11, 2022)