Here’s how you can have a Global Price List under an Org Unit without tying it to the currency of the base Org Unit which is the Default use case.
Currently, here’s how the default behavior is without having the multi-currency cost price list disabled – 
Now, let’s see how this will change when we have the Multi-currency cost price list enabled for your environment.
Multi-currency Cost Price List
This can be enabled from Project Parameters. Here’s how you do this provided you have the correct access –
- Go to Project Parameter record in PO Lite, you’ll see this – which you can select Yes and save to enable it.

- When you enable, it’ll show this message before you confirm –
“You are changing the way a Cost Price List is selected by system. The setting you are choosing indicates that the system will no longer select a cost price by matching the currency of the price list with the currency of the contracting unit. Any cost price list irrespective of currency could be selected as long as it is applicable for the date. Please ensure that you understand the impact before making this change. Please note that this will impact cost price list defaulting for ongoing projects as well.“ - Now, when you have the same enabled, you’ll be able to add a Cost Price list of different currency than that of the Organization Unit.

- If you see above, the different currencies can exist for the Organization which has a certain currency.
Behavior
Here’s a caveat when you select a multi-currency Cost Price List still
- You cannot have the Start and End Dates overlap each other even when you have different currencies. When you try to do this, it’ll give you the below error.

- When Time Entries are made, the Inter-Organizational Sales Actuals are also created based on the Cost Price from that Price List.


Being able to schedule for Resources across multiple geographies
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate
Thank you!