Answers.Body: <p>It seems something changed and is now case-sensitive. This fixes it for me: <a href="https://github.com/civicrm/civicrm-core/pull/30189" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/30189</a></p>
  <p>It's a one-letter change in CRM/Case/XMLProcessor/Report.php on line 962. Change</p>
  <p><code>$extends = ['case'];</code></p>
  <p>to</p>
  <p><code>$extends = ['Case'];</code></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-14T18:38:25.297Z
Answers.Text: Yup, that fixed the issue for me. Thanks!
Answers.UserDisplayName: zip
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-14T18:30:59.390Z
Answers.LastActivityDate: 2024-05-14T18:30:59.390Z
Answers.UserDisplayName: Demerit
Body: <p>We're in the midst of upgrading (5.69 &gt; 5.71), and I noticed that when viewing a case, if I click on Print Report, none of the custom fields appear on the print view on our 5.71 dev site. They appear fine on our 5.69 production site.</p>
  <p>I've checked several of the demo sites available, and I see them there sometimes and not other times, but I can't consistently see the version numbers on the demo sites to know what I'm actually comparing.</p>
  <p>I'm just trying to determine if this is a general problem or a just-us problem. Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-05-14T18:01:28.950Z
Comments.Text: The version number appears at the bottom of every civi page.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-05-14T18:03:04.350Z
Comments.Text: On a lot of the demo sites it doesn't. I went through all of the english languages ones listed here: https://civicrm.org/demo and some do and some don't. Like this one doesn't: https://demo.symbiotic.coop
Comments.UserDisplayName: zip
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-05-14T18:11:48.067Z
Comments.Text: Oh ok 3rd party ones might have a different theme that doesn't show it. When you say custom fields, do you mean fields on CASES or on ACTIVITIES. I'm not sure CASE custom fields will appear on the print report?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-05-14T18:21:03.560Z
Comments.Text: I think I see the problem. Give me a couple minutes.
Comments.UserDisplayName: Demerit
Tags: <civicase>
Title: Custom Data Fields not showing on Case Print Report
ThreadText: # Custom Data Fields not showing on Case Print Report
  
  (Asked by: username_0 on 2024-05-14)
  
  We're in the midst of upgrading (5.69 > 5.71), and I noticed that when viewing a case, if I click on Print Report, none of the custom fields appear on the print view on our 5.71 dev site. They appear fine on our 5.69 production site.
  
  I've checked several of the demo sites available, and I see them there sometimes and not other times, but I can't consistently see the version numbers on the demo sites to know what I'm actually comparing.
  
  I'm just trying to determine if this is a general problem or a just-us problem. Thanks!
  
  **Tags:** civicase
  
  > **Comments:**
  > **username_1**: The version number appears at the bottom of every civi page.  
  > **username_0**: On a lot of the demo sites it doesn't. I went through all of the english languages ones listed here: https://civicrm.org/demo and some do and some don't. Like this one doesn't: https://demo.symbiotic.coop  
  > **username_1**: Oh ok 3rd party ones might have a different theme that doesn't show it. When you say custom fields, do you mean fields on CASES or on ACTIVITIES. I'm not sure CASE custom fields will appear on the print report?  
  > **username_1**: I think I see the problem. Give me a couple minutes.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-05-14. Score: 2 | Accepted answer
  
  It seems something changed and is now case-sensitive. This fixes it for me: <https://github.com/civicrm/civicrm-core/pull/30189>
  
  It's a one-letter change in CRM/Case/XMLProcessor/Report.php on line 962. Change
  
  `$extends = ['case'];`
  
  to
  
  `$extends = ['Case'];`
  
  > **Comments:**
  > **username_0**: Yup, that fixed the issue for me. Thanks!  
  
  ---
  
  