Skip to content

[IDEA] Manual KPIs #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sbidoul opened this issue Apr 16, 2019 · 6 comments
Open

[IDEA] Manual KPIs #173

sbidoul opened this issue Apr 16, 2019 · 6 comments

Comments

@sbidoul
Copy link
Member

sbidoul commented Apr 16, 2019

  • a new model (MIS Manual Kpi Value) that inherits from the abstract mis.kpi.data, which already exists and is the basis for mis budget items
  • a flag manual on mis.report.kpi
  • when evaluating a report, lookup manual kpi values in the new table, using mis.kpi.data_query_kpi_data(), similar to what is done in mis_builder_budget
@pedrobaeza
Copy link
Member

Isn't this similar to current cash flow concept creating an auxiliary table for manual entries?

@sbidoul
Copy link
Member Author

sbidoul commented Apr 16, 2019

@pedrobaeza I'm not sure

@sbidoul
Copy link
Member Author

sbidoul commented Apr 16, 2019

Problem: with this, manual applies to the whole row, independently of the source set in columns. So one cannot budget (for instance) on a manual kpi. Not good as is.

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jan 23, 2022
@sbidoul sbidoul reopened this Apr 2, 2024
@sbidoul sbidoul removed work in progress stale PR/Issue without recent activity, it'll be soon closed automatically. labels Apr 2, 2024
Copy link

github-actions bot commented Oct 6, 2024

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.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 6, 2024
@sbidoul sbidoul removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 6, 2024
Copy link

github-actions bot commented Apr 6, 2025

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.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 6, 2025
@sbidoul sbidoul removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants