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

[10.0] [MIG] hr_expense_move_date #393

Closed

Conversation

nikul-serpentcs
Copy link
Member

Expense Move Date

Add move date to expense.
Allows user to force a specific move date

@nikul-serpentcs
Copy link
Member Author

@aheficent Could you please review.

Commits are already preserved and can you please check the history

Copy link

@AaronHForgeFlow AaronHForgeFlow left a comment

Choose a reason for hiding this comment

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

Cannot post the journal entry from the expense:
image

Copy link

@AaronHForgeFlow AaronHForgeFlow left a comment

Choose a reason for hiding this comment

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

Failing when trying to post the journal entry from the expense:

image

@nikul-serpentcs
Copy link
Member Author

@aheficent Improved code Could you please review.

Copy link

@AaronHForgeFlow AaronHForgeFlow left a comment

Choose a reason for hiding this comment

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

👍 It works fine now

@feketemihai
Copy link
Member

My opinion is that the module should not be ported anymore, since the expense have a dedicated accounting_date field, which overwrites the date of the expense, it's nonsense to add a new field move_date which does the same as accounting_date...

@AaronHForgeFlow
Copy link

@feketemihai what's that accounting_date field? I did not find it on the hr_expense module

@feketemihai
Copy link
Member

@aheficent After you submit to manager, the expense appears in the Expense Report, where you can input the accounting date which you post the expense...

@feketemihai
Copy link
Member

On submit to manager, Odoo creates an expense sheet,

https://github.com/odoo/odoo/blob/10.0/addons/hr_expense/models/hr_expense.py#L45

the sheet have a field accounting_date, which you can modify, if not set the move is created with the expense date.

@feketemihai
Copy link
Member

@AaronHForgeFlow
Copy link

you're right @feketemihai I'd close this

source

@feketemihai
Copy link
Member

@nikul-serpentcs @aheficent To make it easier, not to move from expense to expense sheet to post the moves, you can add the related 'accounting_date' field from sheet_id to expense, with oldname=move_date, and after you send to approval, you can modify accounting_date of the sheet from expense, and to post directly from expense.

@nikul-serpentcs
Copy link
Member Author

@aheficent @feketemihai Improved code Could you please review.

@feketemihai
Copy link
Member

@nikul-serpentcs Sorry for guided you wrongly, i didn't folow all the process of expense, so the accounting_date is already shown in the expense after the state is changed to approve, so no need for this module, apologizes again...can you also try with odoo runbot the workflow...

@AaronHForgeFlow
Copy link

AaronHForgeFlow commented Nov 14, 2017

@feketemihai but if the field in the expense is related it cannot be different to the one in the sheet, right? Two fields have to be maintained then.

Update: @feketemihai did not see your last answer. Do you agree to close this then?

@feketemihai
Copy link
Member

@aheficent yes... I will add in the migration issue as deprecated

@pedrobaeza pedrobaeza mentioned this pull request Nov 14, 2017
58 tasks
@nikul-serpentcs nikul-serpentcs deleted the 10.0-hr_expense_move_date branch January 9, 2018 11:56
sambarros pushed a commit to sambarros/hr that referenced this pull request Jul 26, 2018
[BSSFL-516] Team on journal items list view
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants