Performance impact of having all currencies in an app ?

Hi Sergey​ , the currencies that you see there on the Application Properties tab are the 'eligible' currencies that you can now assign to an Entity.  They don't actually come in to play in your application until they are assigned to an Entity.  There is no performance impact to listing all of the currencies - making them available - on the Application Properties tab.  But why would you want to?  

I would clear out all Currencies you are not using from the Application Properties tab.  When users are in ad hoc mode building a Quick View or selecting Consolidation Dimension on their Session POV tab - the Currencies are now available for your users to select.

You probably don't want users to get confused as to why all available currencies are selectable here if they are not assigned to an Entity and not valid in your application.

Regards,

Mike G

Potentially you might end up with more dataunits, which means more records in the database. This may or may not be an issue, depending on the volume of data and how many currencies you actually have numbers for. Same for Translations - if not careful (e.g. if you translate to all available currencies), you might end up with a lot of extra numbers. 

A practical advice to update Currencies that is easier and faster than "Currency" pick list.
- For a mass update, use Notepad++ to create a new list to copy/paste into "Currency Filter" box.
- For a minor update, work them in "Currency Filter" box.