Contextual (CRMAF_/Data Pre-Filtering) SQL-based reports don't seem to work in CRM 2011

Proposed Answer Contextual (CRMAF_/Data Pre-Filtering) SQL-based reports don't seem to work in CRM 2011

  • 11 มีนาคม 2554 2:52
     
     

    Here's my query:  SELECT CRMAF_FilteredContact.fullname from FilteredContact AS CRMAF_FilteredContact

    I've followed all instructions for deploying the report.

    It works for a report built with the wizard...however, I see it's a Fetch XML-based report.

    I've seen a number of posts regarding problems in this area, but I have not seen any successful resolution for these.

    Any help appreciated.

ตอบทั้งหมด

  • 11 มีนาคม 2554 12:45
     
     

    Hi

    Can you please send your RDL file to abhia_at_microsoft_dot_com? I will take a look.

    Thanks


    Abhishek Agarwal MSFT
  • 14 เมษายน 2554 19:43
     
     
    I had a problem with bringing CRMAF reports from CRM 4 to CRM 2011.  CRM 2011 was installed on a new server and the CRM 4 organization was imported.  The database name on CRM 4 was organizationname_MSCRM and the CRM 2011 database name was organizationname.  So I went into the reports and updated the data source connection string and none of them worked and then by chance I realized that one of the reports I forgot to change the data source and it was working fine (it was pulling data from the new database even though the connection string was pointing to the old database), so I went back into the other reports and appended _MSCRM to the database name and the reports started working again.  They are pointing to a database that doesn't exist, so I don't know what is going on, but I got them to work.
    Dave
  • 4 พฤษภาคม 2554 22:19
     
     

    Hi There -- I just upgraded CRM 4.0 to CRM 2011 and then applied RU1. My custom reports with pre-filtering all broke and returned all records instead of filtered records. I fixed this by simply going to the report, clicking edit, actions, Download Report and I saved the rdl file. Then I re-uploaded the same rdl file to the exact same report that I just downloaded. This somehow fixed the pre-filtering. Sounds like it might be an upgrade bug.

    Best,

    Phil


    Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspx
  • 6 พฤษภาคม 2554 3:26
     
     

    Hi Phil,

    The custome reports you are talking about, were they created using Report Wizard in CRM 4.0  or uploading an existing file?

     

    Regards,

    Rahul

  • 6 พฤษภาคม 2554 17:15
     
     

    Hi Rahul -- these were fully custom from scratch existing file SSRS reports.


    Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspx
  • 10 พฤษภาคม 2554 3:29
     
     
    Has there been a resolution to this issue yet? We have an extensive set of custom reports mostly from existing 4.0 environments that are experiencing the same issues as Phil. Ours are also SSRS created from scratch that use the CRMAF prefix on queries.
  • 10 พฤษภาคม 2554 4:45
     
     

    Hi Phil and Ryan,

    What I meant by my question was that how did you bring these reports in CRM? Did you create them using Report Builder and uploaded the report in CRM using "Upload an existing file" option when you create a report in crm 4.0 or did you create the reports using the Report Wizard in crm 4.0?

    From your response, I am assuming that you created the reports outside of CRM and then uploaded them in CRM. If that is the case, then there should not be any problem because they work as they used to work before upgrade.

    Can any of you send an upgraded report RDL that seems to have issues at rahula@microsoft.com.

    Thanks,

    Rahul

  • 10 พฤษภาคม 2554 15:19
     
     

    Rahul, I created my reports in Visual Studio for SSRS and then uploaded to a common environment to our team's custom solution. These reports all worked fine in 4.0.

    When I import our custom solution into a different 2011 instance, the reports stop using the CRMAF filter and simply either return the top record or the entire dataset. If I then manually browse into that instance and upload the exact same .rdl file that was in the solution the CRMAF filter works fine. This is a problem though as we have multiple reports in multiple instances that I don't want to have to manually update everytime we deploy a solution update.

    Also whenever we import an update to the solution the reports revert back to not applying the CRMAF filter.

    I will email you one of our .rdl files.

  • 10 พฤษภาคม 2554 16:59
     
     

    HI Rahul -- I used BIDS to create the RDL, and then I used the CRM UI to deploy the RDL file via existing file upload in 4.0. Then I ran the upgrade and it broke. Then I re-downloaded the RDL via the CRM UI in 2011, and re-uploaded it via the CRM UI in 2011, and that fixed the filtering. I understand that they should work as they used to work before, but they do not without this workaround.

    I no longer have access to upgraded RDLs that had the issue because I've already applied the workaround to all reports -- hope Ryan's RDL helps!

    Best,

    Phil


    Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspx
  • 13 พฤษภาคม 2554 18:34
     
     คำตอบที่เสนอ

    Did find one additional workaround that I will probably use for now. Basically if I delete the reports completely out of my CRM instance then re-import my solution file the contextual filtering works. Its only when importing a report into an environment where that report already exists, either in the default solution or our custom one, does the filtering break.

    So basically we are placing all of our custom reports into its own custom solution, then whenever we deploy an update to any report we'll just delete all the reports from the instance, then import the updated solution. This seems to resolve the problem and is at least easier then manually updating each report.

    Hope this helps,

    Ryan


    • เสนอเป็นคำตอบโดย Isil AP 16 สิงหาคม 2554 14:19
    •  
  • 22 กรกฎาคม 2554 20:09
     
     

    Ryan,

     

    We have investigated the issue you mentioned here and it is definitely a bug. We have filed a bug for this and are working on the solution. 

     

  • 28 กรกฎาคม 2554 21:09
     
     

    Hi Phil

    Do you have the original RDL that you created using BIDS and then uploaded to CRM 4.0? If yes, please send it across to abhia_at_microsoft_dot_com. We have found the problem with solutions import export but haven't really found the upgrade bug.

    Also, did you do an inplace upgrade from CRM 4 to 2011 or an import organization?

    Thanks

    Abhishek


    Abhishek Agarwal MSFT
  • 16 สิงหาคม 2554 14:18
     
     

    I had the exact same issue repro with brand new CRM 2011 SSRS report (i.e. not an upgrade from 4.0). The workaround to download and re-upload worked only after I deleted the original version. Thanks for the workaround!

    Isil

  • 25 พฤษภาคม 2555 23:58
     
     

    Hello,

    Did this ever get solved because I think we're still seeing it.  I thought it was related to SDK loading of reports, but are still getting it if updating the report RDL via the UI.

    http://social.microsoft.com/Forums/en-PH/crmdevelopment/thread/5e8d0138-647c-4e7b-a8b6-02f1c2641693

    Thanks

    Glenn

  • 28 พฤษภาคม 2555 0:18
     
     

    Solved the issue by creating another solution which host the reports only and uninstalling everytime.

    I've added a bug to Microsoft Connect - https://connect.microsoft.com/dynamicssuggestions/feedback/details/744377/contextual-crmaf-data-pre-filtering-sql-based-reports-dont-work-in-crm-2011-if-updated-via-solution#tabs


    • แก้ไขโดย glenn_goodwin8 28 พฤษภาคม 2555 0:19
    •