4 answers
Hi RajeshRemove the "run as specific user" completely from the dashboard prior to deployment (set the options to "Run as logged-in user"). Deploy, then change it back to whatever you need.It tries to find an user by username (in XML of the dashboard definition the reference is stored by username, not by User Id or email). And obviously fails because in production you don't have same sandbox suffix. Same happens when you try to deploy a report/dashboard that's scheduled to be sent to some users or when email alert (from workflows) is being deployed...Easiest fix is to remove these settings, deploy the "core" of dashboard and amend it manually in the target org.Alternatively you can temporarily change the username in your target org to be same as the sandbox username (it shouldn't cause login conflicts because the endpoint will still be either login.salesforce.com or test.salesforce.com)... but I believe you'll hit the lockdown of allowed domain names in your production.Also follow the below links:http://salesforce.stackexchange.com/questions/12195/dashboard-deployment-errorshttps://success.salesforce.com/answers?id=90630000000gwabAAAPlease do let me know if it helps you. Regards,
Mahesh
