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
Currently: When a record is imported into the portal, often times if a value is blank, it is assumed that the service doesnt exist. e.g., multi-select or single select fields.
The result is that it is displays as "There is currently no information for this facility"
Expected: Some users are expecting that it would rather show; "Service doesn't exist" or be blank.
Let's sort out some way to resolve either in the tool or through better process/data spec during collection/import.
Priority: Medium
The text was updated successfully, but these errors were encountered:
The optics of the string, are that the data was not collected. When in reality it was; but the spec doesnt clarify that the service isnt there vs. missing.
Currently: When a record is imported into the portal, often times if a value is blank, it is assumed that the service doesnt exist. e.g., multi-select or single select fields.
The result is that it is displays as "There is currently no information for this facility"
Expected: Some users are expecting that it would rather show; "Service doesn't exist" or be blank.
Let's sort out some way to resolve either in the tool or through better process/data spec during collection/import.
Priority: Medium
The text was updated successfully, but these errors were encountered: