This is massive set back. I asked about it today in the Product Update Briefing for Australia. I got a 'meh' answer that just brushed me off. 'We're looking at it and we'll let you know if we decide to do anything about it'. It's going to make all our lives so much more difficult - sort it out BB!

Absolutely ridiculous. What a set back. I thought new systems were supposed to make things more efficient where this is making for more work. We have multi-year grantees and now I have to go and set up multiple requirement forms where in the legacy we were able to reuse the same form. Get rid of this new system. What about it is making it more efficient?

This is a massive headache for us. We have hundreds and hundreds of grants with different reporting cadences, many of them multiyear grants that have the same requirement type multiple times over the course of the grant term. We have about 6 unique report forms that will be used multiple times for various grants. The current system design will require us to create at least 4 or 5 versions of each form with different names, all of which are visible to grantees in the new portal and email notifications. Further complicating this situation is the lack of a clear way to display which requirement forms have already been published to a request in order to know which form needs to be published for the next requirement.

This issue was re-raised today in one of my local group BBGM user forums, and it seems open to so much data insecurity in terms of sharing applications within organisations between senior and administrative roles, and with users re-applying multiple times for grants where previous attachments are appearing and confusing the situation. I am really concerned about this currently and worry it may mean ceasing using the uploading tools until resolution.

This is an issue for us as well. Be aware that using the same form multiple times has shown us through testing that the previously submitted information in form #1 will be carried into form #2, thus pre-populating the form with old information. If you're looking for updated/new attachments or information, the user will need to delete/remove the old information, and enter/upload the new information. I foresee a LOT of incorrect/outdated information being collected with the new system.

Regarding the issue with publishing the same form multiple times, the issue seems to mainly be the dates published window. If a form is open from January 1 to March 31, you can't publish the same form again until AFTER the first form is closed. So you can publish again April 1-xxx, etc. The dates can't overlap (another difficulty for us as well).

Our workaround was to create 4 requirements to ensure the dates won't overlap: Fall, Winter, Spring, Summer (our requirements/payments are always the same time periods, so this will work for us). However, this means that Fall year 1 responses will be auto populated into the Fall year 2 form when it comes time to publish that requirement for the 2nd time.

I agree being able to have the same form for multiple requirements on the same request would be beneficial to keep things orderly.