-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
[15.0][MIG]analytic_partner: Migration to 15.0 #515
Closed
bizzappdev
wants to merge
22
commits into
OCA:15.0
from
BizzAppDev-Systems:15.0-mig-analytic_partner-BAD-TUG
Closed
[15.0][MIG]analytic_partner: Migration to 15.0 #515
bizzappdev
wants to merge
22
commits into
OCA:15.0
from
BizzAppDev-Systems:15.0-mig-analytic_partner-BAD-TUG
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Classify analytic items by partner ================================== This module adds a partner on each analytic item for allowing to have another dimension for analysing data. It also handles the proper propagation of this field to the created analytic entries when validating invoices. Configuration ============= You have to be granted as at least "Accountant" in your user profile and have checked the "Analytic Accounting" access right. Usage ===== Go to Accounting > Analytic Journal Items, and there, you can set the partner for the analytic items, and search or group by it. You can also go to a partner, and click on the smart-button "Cost/Revenue", placed on the upper-right part, and you will navigate to the analytic items associated to this partner. Known issues / Roadmap ====================== * This module hasn't been tested with *account_analytic_plans* module installed, so maybe it's incompatible with it.
* IMP: Distinguish between the partner of the account and the specific partner * FIX: Allow grouping on partner_id field. Fixes OCA#41 * FIX: README - Indentation is not correct in Known issues.
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/gl/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/ca/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/pt_BR/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/zh_CN/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-14.0/account-analytic-14.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-14-0/account-analytic-14-0-analytic_partner/fr/
Currently translated at 87.5% (7 of 8 strings) Translation: account-analytic-14.0/account-analytic-14.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-14-0/account-analytic-14-0-analytic_partner/fr_FR/
/ocabot migration analytic_partner |
ready for review |
bizzappdev
changed the title
[WIP][15.0][MIG]analytic_partner: Migration to 15.0
[15.0][MIG]analytic_partner: Migration to 15.0
Jan 3, 2023
/ocabot migration analytic_partner |
bizzappdev
force-pushed
the
15.0-mig-analytic_partner-BAD-TUG
branch
2 times, most recently
from
March 9, 2023 06:03
3a37130
to
11039c1
Compare
bizzappdev
force-pushed
the
15.0-mig-analytic_partner-BAD-TUG
branch
from
March 15, 2023 11:32
e40cfa5
to
f149829
Compare
stefan-tecnativa
approved these changes
Jul 3, 2023
pedrobaeza
reviewed
Jul 3, 2023
|
||
To configure this module, you need to: | ||
|
||
#. Go to **Setting > Users > Users** and check you have as at least "Adviser" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These instructions are obsolete.
Superseded by #573 respecting commit attribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.