New Portal - Fields and codes retaining data

Hanna Berhanusdotter

We operate multiyear programs and use the same questions in our reports for years 1, 2, and 3. For example, we consistently ask if there was any underspending, and if so, why it occurred. In the new portal, we are required to create duplicate fields to accommodate each year separately. This is necessary because the portal only allows us to use a field once throughout the life of a program. If we use the same field again, the data will be retained, even if it is collected based on different requirements.

Additionally, we must create three report forms for each program, as we cannot republish the same form multiple times. If we attempt to use the same form again, the applicant will be prompted to resubmit the report they have already submitted.

It has been confirmed that this is functioning as intended. Has anyone considered an alternative solution? If you agree that fields should not retain data between different requirements, I have also added a suggestion for improvement (GMK-I-1779).

Maryann Hayter

@Hanna Berhanusdotter
This is a problem for us also. I'm going to need to explode the number of forms we have because we use one periodic update form across time. So they may submit the same form quarterly over a year of two. Am I understanding it properly to say that i would need 8 periodic report forms to cover a quarterly update across two years?

Hanna Berhanusdotter

@Maryann Hayter That is how I understand it. Seems like a flaw in the system and will make updating a report forms a lot more complicated.