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
Microsoft has made a large investment in BI in 2015, both on-premises and in the cloud. BI offerings across Datazen, R, Excel, Power BI and coming to SQL Server 2016 are huge. Microsoft released a public BI roadmap on where they are headed with their BI stack. Microsoft’s simple goal is to put the power of data in the hands of every business user. This simple goal is inline with the #1 top ranked IT priority according to Gartner.
I enjoy working with SSRS reports and learning new things to help me build out reports that meet our clients’ needs. When a client comes to me with an interesting way they want something displayed or a request for a feature that is unknown to me, I jump at the chance to do it. I love a new challenge and it acts as a learning experience as well. A recent request came to me that required a little creativity on my part. It was to modify the default value of certain report parameters based on the security role the User had in CRM.
Perhaps you wish to provide your Sales Reps with the Customer Statement from Dynamics GP or a report which summarizes order history. We would be able to use pre-filtering to only pull orders in GP for the Account in question or if your Sales Rep is on the road, still allow them to print out a Customer Statement without having to us a VPN to access GP. Great! So, I’ll just upload the report I created into CRM and be able access my external data. Not so fast.