We use email addresses for our usernames, and when importing data using
the 'Import/export data' app I got an error saying that the 'storedBy'
value was too long. Even though in general users can store data and it
records it against their full username.
If you export out a dataset, and try and reload the dataset back into
DHIS2 without changing the username, you still get this error
(screenshot attached). This implies the data import routines seem to
deal with a different datatype than what the database schema actually
stores.
Using v2.20
** Affects: dhis2
Importance: Undecided
Status: New
** Summary changed:
- Error import due to username length
+ Error on data import due to username length
Title:
Error on data import due to username length
Status in DHIS:
New
Bug description:
We use email addresses for our usernames, and when importing data
using the 'Import/export data' app I got an error saying that the
'storedBy' value was too long. Even though in general users can store
data and it records it against their full username.
If you export out a dataset, and try and reload the dataset back into
DHIS2 without changing the username, you still get this error
(screenshot attached). This implies the data import routines seem to
deal with a different datatype than what the database schema actually
stores.
Title:
Error on data import due to username length
Status in DHIS:
New
Bug description:
We use email addresses for our usernames, and when importing data
using the 'Import/export data' app I got an error saying that the
'storedBy' value was too long. Even though in general users can store
data and it records it against their full username.
If you export out a dataset, and try and reload the dataset back into
DHIS2 without changing the username, you still get this error
(screenshot attached). This implies the data import routines seem to
deal with a different datatype than what the database schema actually
stores.
Title:
Error on data import due to username length
Status in DHIS:
Fix Committed
Bug description:
We use email addresses for our usernames, and when importing data
using the 'Import/export data' app I got an error saying that the
'storedBy' value was too long. Even though in general users can store
data and it records it against their full username.
If you export out a dataset, and try and reload the dataset back into
DHIS2 without changing the username, you still get this error
(screenshot attached). This implies the data import routines seem to
deal with a different datatype than what the database schema actually
stores.
Title:
Error on data import due to username length
Status in DHIS:
Fix Released
Bug description:
We use email addresses for our usernames, and when importing data
using the 'Import/export data' app I got an error saying that the
'storedBy' value was too long. Even though in general users can store
data and it records it against their full username.
If you export out a dataset, and try and reload the dataset back into
DHIS2 without changing the username, you still get this error
(screenshot attached). This implies the data import routines seem to
deal with a different datatype than what the database schema actually
stores.
