-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
[12.0][IMP] l10us_form_1099 #41
Conversation
@brian10048 Thank you very much for working on this. I would replace it because we can deduce the same info from one field. We will need a migration script though. If the boolean is True, I would set the most common 1099: 1099-MISC. Here is an example for the 2nd task: For the 3rd and 4th, I updated the issue #36. |
@bodedra I added the report files, but I need help making the SQL query correct |
@brian10048 sure. |
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.
Functional test on runbot. LGTM 👍
/ocabot merge minor |
This PR looks fantastic, let's merge it! |
@brian10048 Please squash your commits. Cc @max3903 |
- Add a new object 'type.1099' with a char field 'Name', - Add a many2one field '1099 Type' on res.partner to type.1099, - Add data for type.1099 with: 1099-A, 1099-B, 1099-C, 1099-CAP, 1099-DIV, 1099-G, 1099-H, 1099-INT, 1099-K, 1099-LTC, 1099-MISC, 1099-OID, 1099-PATR, 1099-Q, 1099-R, 1099-S, 1099-SA, RRB-1099 and SSA-1099 - Add a SQL report object 'account_payment_1099_report' with views - Add security for new objects
Squashed into one commit. Thank you to @bodedra for his work on this as well. The squash cleaned up some of the commits he authored. |
Congratulations, your PR was merged at 352ab5a. Thanks a lot for contributing to OCA. ❤️ PS: Don't worry if GitHub says there are unmerged commits: it is due to a rebase before merge. All commits of this PR have been merged into |
@max3903 This is a start for #36
Do you want to totally replace the boolean field or is this an acceptable option to add another field?
I'm needing direction for the second task of #36
For tasks 3 & 4 of #36, should these reports be in the Contacts app menu?