REPORT VIEWER GUIDANCE FOR TESTING

Following are groupings of Report Name, Web Part Parameters and URL's for use in testing the MX 365 FETCH XML Report Viewer web part.  This section addresses both testing by Context (contactid and accountid) and 'From URL'   For each named report, copy the Parameters  identified in the 'Report parameter(s) read from xxxx' section  of this content and paste into the appropriate setting on the Report Viewer web part Configuration form.  If parameters are being ready 'From URL", pair that with the URL identified in the grouping to successfully run the report.

1.  Report Name:  UX Meeting Confirmation Report: 

• Web Part - 'Report parameter(s) read from URL':    pa_meetingsetupid,pa_participantname
• Meeting Only URL:  https://mx365dev.ptassoc.com/Admin-Resources/Sandbox/QA4?pa_meetingsetupid=c65f4cfe-2a1f-e911-a951-000d3a124c0a 
• Meeting and Participant Name URL:  https://mx365dev.ptassoc.com/Admin-Resources/Sandbox/QA4?pa_meetingsetupid=c65f4cfe-2a1f-e911-a951-000d3a124c0a&pa_participantname=Blair,%20Paul

2.  Report Names:   

1.  UX Chapter Reimbursement Summary 
2.  UX Chapter Reimbursement Detail

• Web Part - Report Schema  parameters - Used ONLY for the report QUERY in UX':    pa_batchdate ,pa_chapterid ,pa_companyid
• User defined parameters mapped to the Report schema parameters and pulled from URL.  *Note that both the web part configuration and URL parameters must be identical:
• pa_batchdate (instance 1) = 'batchdatestart
• pa_batchdate (Instance 2) = 'batchdateend'
• pa_chapterid = 'chapter'
• pa_companyid = 'company'
• URL (AFTER configuring web part :  https://mx365dev.ptassoc.com/Admin-Resources/Sandbox/QA4?batchdatestart=1/1/2018&batchdateend=12/31/2025&chapter=fbb977ab-467a-e811-a974-000d3a1618d5&company=a6d32dc2-387a-e811-a97d-000d3a1612a7 
• URL:  The same URL works for both of the reports above.  Just Select the desired Report name on the Report Viewer web part Configuration form.
• *Note about Date Range/duplicate parameters:  With changes made on 08.26.2022, there is no longer a need to use a comma, or Pipe separator between duplicate parameters.  NOW every parameter is separated by an ampersand (&) and duplicate parameters are managed just like non-duplicate parameter.  Each parameter must use Name=value syntax regardless of whether there are duplicates like in a range or not..

3.  Report Name:   UX Fundraising Setup

• Web Part - 'Report parameter(s) read from URL':    pa_companyid,pa_contributionsetupid
• URL:  https://mx365dev.ptassoc.com/Admin-Resources/Sandbox/QA4?pa_companyid=a6d32dc2-387a-e811-a97d-000d3a1612a7&pa_contributionsetupid=f1427d23-f702-e911-a972-000d3a1c5cc0
• URL:  

Context = 'contactid'

4.  Report Name:   UX Contact Balance Report

• Web part - 'Report parameter(s) read from context:  contactid

Context = 'accountid'

5.  Report Name:  MX Account Balance Report

• Web part - 'Report parameter(s) read from context:  accountid0