You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
One more thing about this pass through MassBuilds that is bothering me. A number of projects that I created in the App were missing essential data, where the fields are flagged in beige, that should have prevented me from creating the project in the first place. Quite a few were missing GFA figures, unit counts or both. I know I always made an effort to enter the latter two fields when these projects were created and don’t think I could have sent them for review had I not done so. What’s more, the land area field was blank for virtually veery project I looked at and again I know I just about always filled that in.
The text was updated successfully, but these errors were encountered:
We have learned after looking at a different issue that it appears MassBuilds will discard submitted values if they do not match the expected type on the backend without any feedback to the user. This may be the source of this issue. Next step for this would be to work on a feature to translate validations to the user side.
Describe the bug
One more thing about this pass through MassBuilds that is bothering me. A number of projects that I created in the App were missing essential data, where the fields are flagged in beige, that should have prevented me from creating the project in the first place. Quite a few were missing GFA figures, unit counts or both. I know I always made an effort to enter the latter two fields when these projects were created and don’t think I could have sent them for review had I not done so. What’s more, the land area field was blank for virtually veery project I looked at and again I know I just about always filled that in.
The text was updated successfully, but these errors were encountered: