Skip to content
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

[17.0][MIG] account_brand #193

Open
wants to merge 52 commits into
base: 17.0
Choose a base branch
from

Conversation

RicardCForgeFlow
Copy link

Migration to 17.0

@ForgeFlow

1. Go to Accounting \> Customers \> Invoices
2. Select or create an invoice
3. Enter the information and select the brand
4. Print the PDF report. It includes the information of the brand.
Copy link

@GuillemCForgeFlow GuillemCForgeFlow Mar 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see point 4 implemented. Is it?
Perhaps any of you can help me with that? 😄 @sbejaoui @RLeeOSI @osi-scampbell @max3903 @cubells @AmmarOfficewalaSerpentCS

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GuillemCForgeFlow
I think that point 4 is https://github.com/OCA/brand/pull/205/files

To use this module, you need to:

  1. Go to Settings > Users & Companies > Brands
  2. Add a new brand or select an existing one
  3. Enter brand information and select the a layout
  4. Go to any branded object abd print the PDF report. It includes the
    information of the brand.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase for merge it?

Copy link

There hasn't been any activity on this pull request in the past 4 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 PR 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 Jul 14, 2024
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 28, 2024
vimalpatelserpentcs and others added 17 commits August 2, 2024 10:57
…er can't fill up analytic account on invoice lines
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/
Currently translated at 86.3% (19 of 22 strings)

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/de/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/
Currently translated at 72.7% (16 of 22 strings)

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/hr/
Currently translated at 100.0% (22 of 22 strings)

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/hr/
Currently translated at 100.0% (22 of 22 strings)

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/es/
Currently translated at 100.0% (22 of 22 strings)

Translation: brand-16.0/brand-16.0-account_brand
Translate-URL: https://translation.odoo-community.org/projects/brand-16-0/brand-16-0-account_brand/es_AR/
Copy link

@FernandoRomera FernandoRomera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@bosd bosd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional review..
Left V16 right V17 runboat of this pr.
Something very important is missing 😉

image

@GuillemCForgeFlow
Copy link

@bosd guessing that's what you were mentioning, right?

@bosd
Copy link

bosd commented Nov 6, 2024

@bosd guessing that's what you were mentioning, right?

Indeed, the brand field was not visible in the view. 😉

@RicardCForgeFlow
Copy link
Author

Hi @bosd and @GuillemCForgeFlow.
Since the PR was made to now the original view of the account module has changed. Now you should be able to see the brand field.

Thank you very much for the help 😄

("internal_type", "=", "receivable"),
("deprecated", "=", False),
]
return {"domain": {"account_id": domain}}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not work in v17 anymore. Instead, you could create a computed field for which you'd assign a domain to be then used in the view

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch 🤾

<field name="model">account.move</field>
<field name="inherit_id" ref="account.view_move_form" />
<field name="arch" type="xml">
<field name="partner_shipping_id" position="before">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still can't see the field in the runboat 🤔 perhaps we'll need to analyze in more detail how to add it to the view.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disregard this comment, I needed to activate the brand_use_level. we could perhaps make it more explicit in the documentation?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I needed to activate the brand_use_level. we could perhaps make it more explicit in the documentation?

Fell into the same trap. 😿 That would be a good improvement.

@bosd
Copy link

bosd commented Nov 6, 2024

Thank you very much for the help

You owe me a 🍺 at the next oca days / oxp 😆

The field is there now 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.