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

[User Story]: Convert File Version #511

Open
ClaireValdivia opened this issue Nov 18, 2024 · 0 comments
Open

[User Story]: Convert File Version #511

ClaireValdivia opened this issue Nov 18, 2024 · 0 comments

Comments

@ClaireValdivia
Copy link

Why is this issue important?

It is not easy to copy/paste info from an old version of an import template into a new version because the excel templates are heavily customized with conditional formatting. Especially when treasury makes last minute changes, it is helpful for partners to be able to convert an upload file from an old version to the most up to date version.

Current State

Partners need to manually re-enter data from old input templates into the new versions as soon as they are available.

ARPA has a way to "import" data from an old version to a new version using macros but this does not exist for CPF.

Expected State

On uploads page, there is a new button to "Convert file version"
When you click this, it brings you to a new page with the following fields:

  • Choose file: this allows you to select a file from your computer that you want to convert.
  • Button display below this with the text "Convert file to [active version number]"
  • When you click the button, it should download an excel file to the user's computer that reflects the content of the uploaded file, but using the Output Template version number used for the organization's active reporting period.

Requirements for the new file:

  • On the Cover tab, the EC code should reflect the value submitted for the EC code on the uploaded file if a value was selected. If no value was submitted, it should show as blank in the new file.
  • The new file should "import" data to the new template for any fields that have matching IDs (row 3 for project & subrecipient tabs).
  • If the new version has a new field not found in the submitted template, the new field's value should display as blank for any imported records.
  • If the new version removes a field that existed in a previous version, that field should not be "imported" to the new version.

Implementation Plan

The following functions need to be added...

Relevant Code Snippets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Scoping
Development

No branches or pull requests

1 participant