通过 VPN 访问 CRM 过滤视图
我目前正在为 Microsoft CRM 开发一组报告。我使用 Visual Studio 2005 从本地开发计算机创建和设计 RDL 文件，该计算机位于与客户端不同的网络上。我可以通过 VPN 并使用 SQL Server 用户登录来访问 CRM 数据库，该登录不是 CRM 中的 Active Directory 用户设置。
我需要使用 CRM 数据库中的筛选视图，但由于在从 Visual Studio 连接时我没有以 Active Directory 用户身份登录，所以我没有收到任何查询结果。
我已经看到了一些人建议的解决方案，您可以在执行查找之前使用“EXECUTE AS USER = 'domain\user'”，但我无法使用远程域用户，因为在查询时出现以下错误：
“无法执行为数据库主体，因为主体“DomainEx\usernameEx”不存在，无法模拟此类主体，或者您没有权限。”
当您不在本地域上下文中时，有人可以为我提供一些有关如何在报告开发过程中使用过滤视图的指导吗？
I'm currently developing a set of reports for Microsoft CRM. I'm using Visual Studio 2005 to create and design the RDL files from my local development machine which sits on a different network from the client. I have access to the CRM database through VPN and by using a SQL Server user logon which is not an Active Directory user setup within the CRM.
I need to use the filtered views from the CRM database but as I'm not logged in as an active directory user whilst I'm connected from Visual Studio I do not receive any results from my queries.
I've seen the solution some people have suggested whereby you use "EXECUTE AS USER = 'domain\user'" before performing the lookup but I cannot use a remote domain user as I get the following error upon querying:
"Cannot execute as the database principal because the principal "DomainEx\usernameEx" does not exist, this type of principal cannot be impersonated, or you do not have permission."
Can someone please provide me some guidance on how to use the filtered views during report development when you are not in the local domain context?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
为了查询过滤后的视图，您需要以 CRM 中使用 Windows 身份验证的 Active Directory 用户身份执行此操作。经过 SQL 身份验证的会话将不起作用。尝试根据视图开发报告，一旦获得正确的外观和感觉，只需将视图重命名为筛选视图，然后部署即可。这将是完成此任务的最简单方法。
In order to query against the filtered views you NEED to do so as an active directory user that is in CRM using Windows Authentication. A SQL authenticated session won't work. Try developing your reports against the views and once you get the look and feel right simply rename the views to filtered views and then deploy. That'll be the easiest way to get this done.