My users are providing a steadily increasing number of distinct Excel files containing user metadata. The files use the proper NPrinting import syntax. Some of the files contain metadata for some of the same users. I want to effectively process these files so as to both populate the NPrinting user database and maintain its accuracy.
Through much trial-and-error, it seems I need one import task containing multiple steps/files. I've created the task but the results are confusing.
My import task has following Merge Policy for each file: User Merge Key: Name Entity Merge Policy: Update Missing Association Merge Policy: Ignore At the bottom of the task, all of the settings are enabled.
The task is erasing some users' domain account information -- resulting in those users losing the ability to login to the web console. This is even occurring after I've manually entered the users' domain account information using the web console.
The domain account is missing for some/all of the users in some/all of the files -- so when the import task runs, the domain account is erased for those users. I've found a quick fix: Adding, to the import task, a manually-maintained Excel file that contains just the problematic users and their domain accounts. But even with that, and with the above merge policy and task settings, the file has to be placed *first* in the list of files processed. Why would that be? And, given my circumstances, is this a reasonable approach? Suggestions welcome!
Are you also using an LDAP import concurrently with your xlsx file import where both are within the same import task or even a separate LDAP import task?
Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
