Seems there is a restriction in Nprinting where no two users can have the same email address. The restriction goes as far down as being a constraint on the postgres database level. Does anyone know why this is the case? We have a need to have several different users with different settings/filters etc. but with the same email address. Anyone know a way around it?
I could remove the database level constraint against duplicate emails and manually edit users in the database to reference the same email id but its possible there is another reason for the restraint. and I'm reluctant to bypass the front end to get around it, for obvious reasons.
Yeah I'll avoid making any changes directly to the database, I think I'm in for a bad time if I went that route.
We have branches of business looked after by 'Regional Managers'. We wants reports filtered by each of these branches to be sent out to each of our Regional Managers. ie. in table form (RM = Regional Manager)
Branch RM $$$
A Joe $20k
B Meg $40k
C Joe $30k
D Bob $15k
So Joe would receive two separate reports, one for A and one for C.
I wanted to go about this by having a separate user for each Branch, called "Branch A Recipient", "Branch B Recipient" etc.with the appropriate Branch filter attached to each Branch User, but the email for both A and C Branch Users being firstname.lastname@example.org. This way, if the RM for a branch changed, eg Branch A is now maintained by Meg, we need only update the email address for Branch A Recipient to be email@example.com.
Benefit of this is I can also append the User Name to the subject of the published task email so the RMs can tell at a glance which email had which Branch report in them, which I cant do if I use filter cycles...
I solved a similiar case with an import task that updates the managers for the enitity. I then have set-up a level in my excel report so each Entity is placed on its own sheet - so a manager for two entities will get a excel report with two sheets, one for each entity.
I would rather have used the entity as a cycle report instead but I (and the managers) don't like sending the reports inside a zip file.
Going forward i will most likely change from import task to API calls instead - it gives more control and I can only update the important stuff like the filters.
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.