Reporting snapshot fails when previous default corporate currency is disabled
Trailblazer Community

Reporting snapshot fails when previous default corporate currency is disabled

Operational Analytics - Reports

Last updated 2019-10-12 ·Reference W-5938730 ·Reported By 1 users

Fixed - Winter '20

Summary
An organization has a currency designated as the corporate currency, then enable Multi-currency and add other currencies, then disable the original currency. This can cause an error when running a reporting snapshot, or other automated record creation, as the process attempts to write the original (now inactive) currency to the records.

Repro
1. Navigate to Setup (top right of Classic/Aloha view, easier to repro this all in classic but same issue in LEX) > on the left side menu type "Company Information" in the Quick Find / Search box and click into the link
2. Click Edit on the resulting detail page > then check the box for "Activate Multiple Currencies" it will default to whatever Currency Locale field is above e.g. USD > Click Save
3. On the Company Information detail page again click the "Currency Setup button" > Then click "New" button > Select a new currency in Currency Type e.g. CAD - Canadian Dollar > Set Conversion Rate to 1.0 and click Save
4. Click on the "Change Corporate" button and from the New Corporate Currency picklist select CAD - Canadian Dollar (or the currency you created) and click Save
5. Click Deactivate beside your default currency that you enabled with Multiple Currencies in step 4 e.g. USD
6. In Quick Find / Search box in Setup again search for "Objects" and click on Objects under Create section > Click the New Custom Object on the resultant page
7. Set the Label to "Account Count", Plural Label to "Account Counts" , check the boxes for :
8. Allow Reports
9. Launch New Custom Tab Wizard after saving this custom object
10. Click Save when done
11. Under "Custom Fields & Relationships" click the "New" button > Select Number for the Field Type and click Next > Set the Field Label to Count, press Tab key to auto-populate the rest of the fields and click Next > Next > Save.
12. Navigate to Reports tab > Click New Report button > Expand Accounts & Contacts folder > Select Accounts > Click Create button > Change the Show to All Accounts, Range to All time and make sure you have account records returning (if not create at least 1 account record)
13. Set the Format from Tabular to Summary Format (IMPORTANT)
14. Save the Report and call it anything e.g. Account Count Report > Set Report Folder to ANY public folder e.g. Unfiled Public Reports and click Save and Run Report.
15. Navigate back to Setup section and in Quick Find / Search type in "Reporting Snapshots" and click the subsequent link
16. Click "New Reporting Snapshot" button > Set the Reporting Snapshot Name as "Account Count", set the Running user as yourself (usually Admin User if you've setup a Developer org in your local, name should be in the top right) > Set Source Report as the Report you created and Target Object as the Object you created.
17. Click "Save & Edit Mappings" button > You should have two drop downs available, for Account Count Name (or whatever you called the custom object) set that to "Reporting Snapshot Name" > for Count (field) set it to "Record Count" and click Save.
18. Next click on the Edit button over the Schedule Reporting Snapshot related list, set the Frequency to Daily, then click on the "Find available options..." link beside preferred start time and pick any time, for dev local orgs you'll only have one option then click Save.
19. Note the error reason after the snapshot has run as "Invalid currency: USD" (or whatever currency you were defaulted as on signup that you deactivated)

Workaround
Re-activate the original currency

Reported By (1)

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS12 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS123 CS137 CS138 CS13 CS133 CS132 CS14 CS148 CS142 CS15 CS152 CS151 CS165 CS16 CS169 CS17 CS18 CS194 CS19 CS198 CS196 CS195 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA130 NA134 NA133 NA136 NA135 NA132 NA131 NA146 NA142 NA141 NA154 NA155 NA172 NA174 NA171 NA173 NA196 NA21 NA37 NA39 NA44 NA45 NA46 NA47 NA49 NA52 NA54 NA57 NA58 NA59 NA61 NA62 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.