You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the mis-builder addon is very powerful and flexible to obtain reports BUT only with respect to move lines and I think that this is a "mistake", that is, I think the addon could be considered as a reporting system at the level of any model.
For example, if we try to make a completely customized sales report, it is not possible, since in the mis.report model, the move_line_sources field only allows me to select move lines.
The changes that occur to me to propose this change with respect to what was previously used would be:
Model mis_report
Change move_line_sources to ir_model (many2one)
Model mis_report_kpi
Change auto_expand_account to auto_expand
Add the auto_expand_field_id field (showing the list of the -ir_field- fields with respect to the model selected in the report and then group the data with respect to this field).
Model mis_report_instance
Delete the target_move field
Add the domain field (Ex: [('type', '=', 'posted')] to simulate what is currently done regarding the entries entered)
Lastly, I think the addon should be available globally as an item in the Odoo menu.
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
Activity
HaraldPanten commentedon Jun 29, 2020
Hi @OdooNodrizaTech ,
You can use MIS Builder for any other model using queries, for example. You can also try with others like bi_sql_editor, bi_view_editor...
Did you consider any of these options?
InformaticaArelux commentedon Jun 29, 2020
Hi @HaraldPanten
I did not know it and the truth can solve many things for me.
HaraldPanten commentedon Jun 29, 2020
Sounds good 👍
I think this issue can be closed, then.
github-actions commentedon Mar 6, 2022
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.