Best Practice for Building CRM Queries in an SSRS Custom Report
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
(or CTRL + M) so you can enable execution plans. In the examples below I will be using tables from AdventureWorks database which is a sample database provided by Microsoft.