-
Notifications
You must be signed in to change notification settings - Fork 10
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: only one row per application in Talpa CSV export #2289
Conversation
[yjdh] Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
[yjdh] Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
[yjdh] Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
[yjdh] Kudos, SonarCloud Quality Gate passed! |
API branch is deployed to platta: https://helsinkilisa-pr2289.api.dev.hel.ninja/healthz 🚀🚀🚀 |
HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr2289.dev.hel.ninja 🚀🚀🚀 |
APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr2289.dev.hel.ninja 🚀🚀🚀 |
TestCafe result is success for https://helsinkilisa-ui-pr2289.dev.hel.ninja 😆🎉🎉🎉 |
Description ✨
Talpa CSV export has multiple rows per application because it uses the same row generation logic as Ahjo export, which generates a row per application calculation row. This PR fixes the Talpa export so, that only one row per application is generated when exporting for Talpa with the prune_data_for_talpa parameter set to True.
Issues 🐛
Testing ⚗️
Create a batch with applications and mark them ready for talpa.
Visit the talpa api endpoint at
/v1/applicationbatches/talpa_export
, to download the CSV.Screenshots 📸
Additional notes 🗒️