Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all
currently the user unique key according to which users a counted in Nprinting 17 is the user e-mail .
is there a way to use the user id instead ,
we work in an enterprise environment where several teams are distributing reports sometime to the same users.
currently if each team try to manage her recipient list via import task we are stuck because , only the first task runs propertly
all ensuing tasks get an error that the a user is already exists.
so the question is can we somehow define nprinting to manage users according to user id and not e-mail ?
second can the import task disregard errors and import all users that don't exists already?
did you follow this?
Do the following:
yes
but you should know that when you import a user via a certain task , if you run another task it want be able to update the user , it appears that in the background the users is attached to a specific import task