Skip to content

[ADD] accounting: add extra fields section to peppol doc#16983

Closed
dade-odoo wants to merge 1 commit into18.0from
18.0-peppol-fields-dade
Closed

[ADD] accounting: add extra fields section to peppol doc#16983
dade-odoo wants to merge 1 commit into18.0from
18.0-peppol-fields-dade

Conversation

@dade-odoo
Copy link
Copy Markdown
Contributor

task-6018915

@robodoo
Copy link
Copy Markdown
Collaborator

robodoo commented Mar 19, 2026

Pull request status dashboard

@C3POdoo C3POdoo requested a review from a team March 19, 2026 13:59
@dade-odoo dade-odoo force-pushed the 18.0-peppol-fields-dade branch from 15561e6 to 92d7912 Compare March 19, 2026 15:08
@dade-odoo dade-odoo requested review from a team and guhec-Odoo and removed request for a team and guhec-Odoo March 19, 2026 15:12
@mcsi-odoo mcsi-odoo requested review from mcsi-odoo and removed request for a team March 24, 2026 09:38
Copy link
Copy Markdown
Contributor

@mcsi-odoo mcsi-odoo left a comment

Choose a reason for hiding this comment

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

Hi Dallas, you're the lucky recipient of my first team doc review 🙈

I've gone into a fair bit of detail in my individual comments, but to summarise a bit:

  • I think we can make this section more concise by introducing and presenting the table data a bit differently, and by renaming the section and removing the sub-headings
  • we also need to clear up any confusion over the Peppol technical field name vs the Odoo technical field name, and I think we can handle the point about the label being used to generate the Odoo technical name mainly as a note (which will also draw more attention to that important point!).

Edited to add: I added this in a comment too, as I knew I'd forget here ... but I just wanted to check if there was a reason you didn't target 17.0 with this change, since I see we already have a comprehensive Peppol section in that version.

Go through my comments in your own time ... see if you can make sense of them ... and then we can discuss in more detail if you like.

Copy link
Copy Markdown
Contributor

@mcsi-odoo mcsi-odoo left a comment

Choose a reason for hiding this comment

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

Hi @dade-odoo , thanks for all the work to integrate my suggestions :)

I think it's going to be worth waiting for my Studio PR to be merged (hopefully r+ing on Monday), so you don't have to duplicate the info about editing a field's technical name (which, after more testing by Audrey, for my own PR, turned out to be lacking some crucial steps).

I'm also still not convinced how we need to formulate that last note / what we need to say about the format of the studio field ... let's discuss that more?

@dade-odoo dade-odoo marked this pull request as draft March 30, 2026 11:47
@dade-odoo dade-odoo force-pushed the 18.0-peppol-fields-dade branch 2 times, most recently from 22bee31 to 1171249 Compare March 31, 2026 07:23
@dade-odoo dade-odoo marked this pull request as ready for review March 31, 2026 07:24
@C3POdoo C3POdoo requested a review from a team March 31, 2026 07:26
Copy link
Copy Markdown
Contributor

@mcsi-odoo mcsi-odoo left a comment

Choose a reason for hiding this comment

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

Looks good to me, @dade-odoo !

@xpl-odoo , could you take a last look for me please?

Copy link
Copy Markdown
Contributor

@xpl-odoo xpl-odoo left a comment

Choose a reason for hiding this comment

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

Great work @dade-odoo as usual! And excellent first review @mcsi-odoo
Very minor comments, I'll let you r+ this one @mcsi-odoo to check if you indeed have r+ rights now!

@dade-odoo dade-odoo force-pushed the 18.0-peppol-fields-dade branch from 1171249 to 52a9593 Compare March 31, 2026 10:38
@mcsi-odoo
Copy link
Copy Markdown
Contributor

Looking good, @dade-odoo !
Will I be able to r+? Let's see ...

@robodoo r+

@robodoo
Copy link
Copy Markdown
Collaborator

robodoo commented Mar 31, 2026

@mcsi-odoo you can't review+.

@mcsi-odoo
Copy link
Copy Markdown
Contributor

@robodoo r+

robodoo pushed a commit that referenced this pull request Mar 31, 2026
task-6018915

closes #16983

Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>
@robodoo robodoo closed this Mar 31, 2026
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.

5 participants