-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add handling for missing data in CombinedInvoiceSupplementReportV2 #11121
Conversation
- also log warning so we can investigate changelog: Bug Fixes, Reporting, Add handling for error seen first day of the month
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.
LGTM
let(:by_iaa_results) do | ||
[ | ||
{ | ||
key: 'IAA123', | ||
year_month: '202408', | ||
iaa_start_date: '2024-08-01', | ||
iaa_end_date: '2025-07-31', | ||
}, | ||
] | ||
end | ||
|
||
let(:by_issuer_results) do | ||
[ | ||
{ | ||
iaa: 'IAA123', | ||
issuer: service_provider.issuer, | ||
year_month: '202408', | ||
}, | ||
{ | ||
iaa: 'IAA123', | ||
issuer: service_provider.issuer, | ||
year_month: '202409', | ||
}, | ||
] | ||
end |
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.
Is it really just a mismatch on year_month between iaas and issuers? I thought the error was happening because an issuer year_month was outside of the range of the iaa.
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.
I feel like the result is the same no?
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.
It should be, it just makes more sense to me now.
Similar to #11095
Differences: