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

Improve error message when a data node is active in the previous period and there is a cashflow import for the next period #302

Closed
dtrzesniak opened this issue May 10, 2023 · 0 comments · Fixed by #348
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@dtrzesniak
Copy link
Contributor

dtrzesniak commented May 10, 2023

Problem is here in the import storage:
// if(allImportScopesNotAtInceptionYear.Any()) {

the error give is generic: Sequence contains no elements

the error should be something like: you are trying to import data for a data node that was active in the previous period, but has no data (i.e the previous partition has not be created, thus the .Single() within the code is empty).

to reproduce, go to Interact With Import Scope Calculation and try to import a cf for a future year (say 2023) to any of the active data nodes we have (without having the previous 2024 year, of course)

@dtrzesniak dtrzesniak converted this from a draft issue May 10, 2023
@dtrzesniak dtrzesniak added the enhancement New feature or request label May 10, 2023
@dtrzesniak dtrzesniak added this to the future milestone May 10, 2023
@dcolleoni dcolleoni added the bug Something isn't working label May 12, 2023
@tkukuljan tkukuljan reopened this Aug 8, 2023
@tkukuljan tkukuljan linked a pull request Aug 8, 2023 that will close this issue
@dcolleoni dcolleoni moved this from 📋 Backlog to ✅ Done in IFRS17 Calculation Engine Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants