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

Fix: Effective Date fix for HDE entries-2769 #2799

Merged

Conversation

prv-proton
Copy link
Collaborator

@@ -178,14 +178,16 @@ def approve(credit_trade, update_user=None, batch_process=False):
Sets the Credit Transfer to Approved
"""
status_approved = CreditTradeStatus.objects.get(status="Approved")
effective_date = credit_trade.trade_effective_date
Copy link
Collaborator

Choose a reason for hiding this comment

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

just want to confirm that on historical data entry, is the trade_effective_date always set? or can it be null?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I checked in the prod table and many records had null value.

@prv-proton prv-proton requested a review from AlexZorkin January 17, 2024 17:49
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.

TFRS - Issues with the effective date for transactions entered using the Historical Data Entry feature
3 participants