0
Excluded

Creating new users (username must be a single data that is not repeated)

sparral 4 months ago updated by Saray Renilla Lamas 3 months ago 2

Good morning.

I'm going to raise this query with an example, see if anyone can give me an idea/solution.

I have María Pérez Fernández (username mperezf)who has been a user of the platform for two years.

It joins the company Martina Pérez Flores, along with 49 other people, and, therefore, I prepare a csv with the data of the 50 new users. The username for Martina is mperezf.

Result: after uploading the csv with the data of the new users, the user of Martina Pérez Flores will NOT have been created and the user of María Pérez Fernández will have become the data (name, surname and all others) of Martina Pérez Florez.

The problem is the matching username. Logically the username has to be a unique data, which is not repeated. But, you shouldn't skip a warning message like "The mperezf user already exists, your data will be modified, are you sure you want to continue?"

Is there a quick way to verify that in the csv there is no username that is identical to that of another user already existing on the platform? I can only automate it, in a way, as follows: export all users already created on the platform to an Excel, add the new ones and search for duplicates. But I still find it a task that consumes an exaggerated time.

Are there any rules that 100% guarantee that a username has not been created before?

We see that the functionality of creating users using csv is very limited, because it only works when the username does not co-indice with any other. If it matches, the information is always overwritten. Also, this happens without you being aware of what's going to happen, because at no point do you get a warning message about what's going to happen (it can take quite a while before you realize the error):

If you checked the S option in the csv, all the data you've put in the csv, including empty data, is overwritten. That is, all the data in the username row will be assigned to the previously existing user and if there is any empty field in the csv, it will also be flushed to the previously existing user.

If in the csv you have checked the option M, do not force the data, so if there is an empty field in Excel, the one that already existed will be respected, but all those listed in the Excel will be assigned to the existing user previously.

Couldn't there be, for example, a "create" C operation, in which data is never overwritten and warned in the event that you try to create a new user with an existing username?

My idea of improvement is that some procedure is enabled to generate new users (not to modify existing ones) by uploading a csv, ensuring that the data of an existing user will not be overwritten.

Answer

Answer
Excluded

ES

Buenas tardes,


Actualmente el tipo de operaciones masivas soportadas por el producto no incluye un "crear" (C) como tal por lo que en este caso concreto la plataforma siempre considera que la información indicada en el CSV es la correcta a sobreescribir y/o mantener y/o borrar. Bien es cierto nada limita que se puedan introducir nuevos usuarios dentro de la plataforma con las operaciones existentes.

La solución sería, como bien se indica en el ticket, sería una nueva funcionalidad dentro las operaciones masivas soportadas, y que se soporte la opción de "crear usuarios" (C) o similar. En este tipo de operaciones ante el caso mencionado se debería lanzar un error de que el usuario ya existe, tal y como ya se está realizando cuando se crea un usuario mediante los mecanismos de creación de usuarios (por ejemplo, a través de pantalla). 

Gracias por la sugerencia!

Saludos,

/Saray

EN

Good afternoon,


Currently the type of massive operations supported by the product does not include a "create" (C) as such so in this particular case the platform always considers that the information indicated in the CSV is correct to overwrite and / or maintain and / or delete. It is true that nothing limits that new users can be introduced into the platform with the existing operations.

The solution would be, as it is well indicated in the ticket, it would be a new functionality within the supported massive operations, and that the option to "create users" (C) or similar is supported. In this type of operations before the mentioned case an error should be launched that the user already exists, as it is already being done when creating a user by means of user creation mechanisms (for example, through the screen).

Thanks for the suggestion!

Regards,


Answer
Excluded

ES

Buenas tardes,


Actualmente el tipo de operaciones masivas soportadas por el producto no incluye un "crear" (C) como tal por lo que en este caso concreto la plataforma siempre considera que la información indicada en el CSV es la correcta a sobreescribir y/o mantener y/o borrar. Bien es cierto nada limita que se puedan introducir nuevos usuarios dentro de la plataforma con las operaciones existentes.

La solución sería, como bien se indica en el ticket, sería una nueva funcionalidad dentro las operaciones masivas soportadas, y que se soporte la opción de "crear usuarios" (C) o similar. En este tipo de operaciones ante el caso mencionado se debería lanzar un error de que el usuario ya existe, tal y como ya se está realizando cuando se crea un usuario mediante los mecanismos de creación de usuarios (por ejemplo, a través de pantalla). 

Gracias por la sugerencia!

Saludos,

/Saray

EN

Good afternoon,


Currently the type of massive operations supported by the product does not include a "create" (C) as such so in this particular case the platform always considers that the information indicated in the CSV is correct to overwrite and / or maintain and / or delete. It is true that nothing limits that new users can be introduced into the platform with the existing operations.

The solution would be, as it is well indicated in the ticket, it would be a new functionality within the supported massive operations, and that the option to "create users" (C) or similar is supported. In this type of operations before the mentioned case an error should be launched that the user already exists, as it is already being done when creating a user by means of user creation mechanisms (for example, through the screen).

Thanks for the suggestion!

Regards,