04-11-2011 08:29 AM
Interesting solution - However, does this not "enable" all users to be able to now merge?
W/our clients, they do not want everyone to be able to do this.
04-11-2011 08:33 AM - edited 04-11-2011 08:36 AM
Unfortunately it does RJ.
Con: Allows all users to merge.
Pro: Doesn't provide other Admin functionality.
Agreed that the best solution would be to provide more roles with more actions.
Provided the user has access to both accounts, then that is all that's required.
04-11-2011 08:39 AM
04-20-2011 11:34 AM
I don't understand this tip and trick. I've deleted the mergeconfiguration.xml file from the Application Architect, and it didn't seem to open up any security related to merging of contacts. Doesn't this file get rebuilt when you convert a lead, also? Maybe I'm missing something, or these instructions are incomplete, but I don't see what this does.
04-21-2011 12:54 AM
04-21-2011 05:18 AM
That doesn't work without the user being an Administrator. So apparently, I've missed something in your procedure. I deleted the MergeConfigurations.xml within the Application Architect and saw that it was no longer in the database.
I don't understand your step number 3 in the SQL approach. "3. Merge the new Account and Contact mappings with the existing global MergeConfiguration.xml file located in the VFS. "
But deleting this file, didn't seem to make any difference for a user that is not an Administrator.