Conversation
After checking the tutorial
Copied from the tutorial
fdardenne
reviewed
Oct 3, 2023
fdardenne
left a comment
fdardenne
left a comment
There was a problem hiding this comment.
Didn't see you created a PR !
It is good, I don't have critical information to share, good job!
I left a few comment just so you can maybe learn a few thing
| name: name, | ||
| res_model: "awesome_tshirt.order", | ||
| views: [ | ||
| [false, "list"], |
There was a problem hiding this comment.
By not including [false, "form"] the user will not be able to open a record in your list view
Author
There was a problem hiding this comment.
Thanks!
I get now that
- the first view type indicates the one that will be open when we click the button
- the view type will only be available if we add it to the
viewslist of doAction
Now, would there be a difference between the second and third view types in the order declared in the views list of doAction?
There was a problem hiding this comment.
Nothing that I know of. Maybe if the second view is not defined then it will take the third view
ABE-Mark45
added a commit
to ABE-Mark45/tutorials
that referenced
this pull request
Nov 30, 2023
Arbaaz-Khan-Tech
added a commit
to odoo-dev/tutorials
that referenced
this pull request
May 1, 2026
- Added SQL constraints to ensure data integrity for offer prices, property tag/type names, and selling/expected prices. - Introduced a new button to automatically accept the best offer for a property. - Implemented a new button to automatically reject offers that are 90% lower than the expected price. - Implemented custom display order logic for various models: - estate.property: Ordered by ID in descending order. - estate.property.offer: Ordered by Price in descending order. - estate.property.tag: Ordered by Name. - estate.property.type: Ordered by Name. Chapter odoo#10 & 11
Arbaaz-Khan-Tech
added a commit
to odoo-dev/tutorials
that referenced
this pull request
May 1, 2026
- Display connected properties in an inline view within the property type XML. - Introduce "Accept" and "Refuse" action buttons in the property offer views. - Configure these buttons to be visible only when the offer status allows the action. Chapter odoo#10 & 11
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.