Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Change user names in Nprinting import file

Hi all,

this seems to be an easy task, however I couldn't find a convenient solution.

I have an excel file that I am using to import all Nprinting users. All the users have unique email address and name as required by Nprinting.

I need to update most of user names (add punctuation). When running the import task I get errors because Nprinting is trying to add these as new users instead of updating existing ones (based on unique email address as a key). Hence I am getting error "email address must be unique".

I know I could delete existing users and run the import task again but then I would have to review all the recipients in the tasks...

Any idea how I could simply change the user names using the excel import file ? I am using Nprinting November 17 version.

Thanks

1 Solution

Accepted Solutions
Ruggero_Piccoli
Support
Support

Hi,

At the moment (April 2018) the import task uses the user name and not the email as primary key for backward compatibility.

So you could:

- if they are a limited number, manually update the user names you want to modify

- if you want to update many users, delete and import them again as new users. Pay attention that when you delete users they are removed from publish tasks. My suggestion to avoid this issue is to associate groups to tasks instead of users, so a user is deleted from the group but the group still remain in the task.

- use the APIs instead of an import task

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.

View solution in original post

5 Replies
blaise
Partner - Specialist
Partner - Specialist

try to get a formal response from Qlik on this one - I find it strange that Username needs to be unique as the email should be enough to uniquely identify a user.

The Import task has a lot of "issues" as I see it I myself thinks it might be better to use the API's instead as you are in more control.

mkelemen
Creator III
Creator III

Hi Kristina,

did you check the "Update users if modified" flag in the import task?

BR,


  Matus

Anonymous
Not applicable
Author

Hi Matus,

yes I had that checked. I thought exactly that if I have that checked the username will automatically update but it didn't.

Ruggero_Piccoli
Support
Support

Hi,

At the moment (April 2018) the import task uses the user name and not the email as primary key for backward compatibility.

So you could:

- if they are a limited number, manually update the user names you want to modify

- if you want to update many users, delete and import them again as new users. Pay attention that when you delete users they are removed from publish tasks. My suggestion to avoid this issue is to associate groups to tasks instead of users, so a user is deleted from the group but the group still remain in the task.

- use the APIs instead of an import task

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Anonymous
Not applicable
Author

Hi Ruggero,

thanks a lot for your answer. I think I will explore the API option and have a second option as plan B

Regards,

Kristina