Answers.Body: <p>I found this on a site we upgrade to 4.7.27 from about 4.7.21 (although possibly it occurred in an earlier upgrade and we didn't notice because we weren't making any changes to the reports). We were using Extended Report extension and upgrading that fixed this for us.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-30T03:51:32.097Z
Answers.LastActivityDate: 2017-11-30T03:51:32.097Z
Answers.UserDisplayName: Gemma - Fuzion
Answers.Body: <p>In our case this was because the 4.6.x sites were using</p>
  
  <ul>
  <li>net.ourpowerbase.reports.advancedfundraising</li>
  </ul>
  
  <p>needed to swop to the newer repo of the code ie</p>
  
  <ul>
  <li>net.ourpowerbase.report.advancedfundraising (without the 's') from</li>
  </ul>
  
  <p><a href="https://github.com/jmcclelland/net.ourpowerbase.report.advancedfundraising/archive/master.zip" rel="nofollow noreferrer">https://github.com/jmcclelland/net.ourpowerbase.report.advancedfundraising/archive/master.zip</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-12T20:29:30.123Z
Answers.LastActivityDate: 2017-04-12T20:29:30.123Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>After upgrading, several sites are missing the Actions on the Reports</p>
  
Tags: <civireport><actions>
Title: Why is the Actions button missing from Reports on 4.7.x after upgrade
ThreadText: # Why is the Actions button missing from Reports on 4.7.x after upgrade
  
  (Asked by: username_0 on 2017-04-12)
  
  After upgrading, several sites are missing the Actions on the Reports
  
  **Tags:** civireport, actions
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-11-30. Score: 1
  
  I found this on a site we upgrade to 4.7.27 from about 4.7.21 (although possibly it occurred in an earlier upgrade and we didn't notice because we weren't making any changes to the reports). We were using Extended Report extension and upgrading that fixed this for us.
  
  
  ---
  
  ### Answer by username_0 on 2017-04-12. Score: 1
  
  In our case this was because the 4.6.x sites were using
  
  * net.ourpowerbase.reports.advancedfundraising
  
  needed to swop to the newer repo of the code ie
  
  * net.ourpowerbase.report.advancedfundraising (without the 's') from
  
  <https://github.com/jmcclelland/net.ourpowerbase.report.advancedfundraising/archive/master.zip>
  
  
  ---
  
  