cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
skoofy5
Continued Contributor
Continued Contributor

Currency Conversion and Formatting in PCF

Hi - I'm trying to create a dataset PCF that formats currency by the logged in users' preference or by the base formatting. I also need to allow for some aggregating, meaning I cannot simply use the formatted value. Does anyone know how I can achieve this in a supported way? How do I retrieve the logged in users currency id?

1 ACCEPTED SOLUTION

Accepted Solutions
skoofy5
Continued Contributor
Continued Contributor

Thanks for the comments guys. Pretty much confirmed what I've already ended up doing earlier today as the only path. I thought I'd let everyone know here if they're after a solution.

 

Below is the query to return both the user's currency preferences, if available, and the base currency. For this particular scenario I'm not interested in the records' currencies as they could potentially vary from one record to the other and so cannot be aggregated, but as Diana pointed out you can grab the currency related to a record if you wish.

<fetch>
  <entity name="usersettings" >
    <attribute name="systemuserid" />
    <filter>
      <condition attribute="systemuserid" operator="eq-userid" />
    </filter>
    <link-entity name="transactioncurrency" from="transactioncurrencyid" to="transactioncurrencyid" link-type="outer" alias="usercurrency" >
      <attribute name="currencysymbol" />
      <attribute name="currencyprecision" />
      <attribute name="isocurrencycode" />
      <attribute name="exchangerate" />
      <attribute name="currencyname" />
    </link-entity>
    <link-entity name="systemuser" from="systemuserid" to="systemuserid" link-type="outer" alias="user" >
      <attribute name="fullname" />
      <link-entity name="organization" from="organizationid" to="organizationid" link-type="outer" alias="userorg" >
        <attribute name="basecurrencyprecision" />
        <attribute name="basecurrencysymbol" />
        <attribute name="name" />
        <attribute name="basecurrencyid" />
      </link-entity>
    </link-entity>
  </entity>
</fetch>

 

So what I have from this is:

 

Base

  • Symbol
  • Precision

User

  • Symbol
  • Precision
  • Exchange Rate

You can then add the "base" (all currency fields have a calculated base field added) columns to the view, or use addColumn to ensure the field is in the dataset:

context.parameters.dataset.addColumn([currencyfield + '_base']);

 

Then I get the unformatted value of the column to do whatever aggregation/maths I need using the base amount, or by taking the value of the base field times by the user's exchange rate I retrieved earlier. In this case I want to be able to switch between the base and users currency.

 

Finally I pass out the formatted value.

context.formatting.formatCurrency(100, 2, $)

 

I was really hoping that somewhere in the dataset info this would have been available already considering what else is already there.

View solution in original post

7 REPLIES 7
skoofy5
Continued Contributor
Continued Contributor

I should say that it's particularly currency conversion and formatting that I'm trying to handle. The base of a currency is always available, but how do I tie this to a currency without an id? How do I also then retrieve the users currency to retrieve the exchange rate?

So the methods that are documented are:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/numberformattingi...

There's also information available through the context:

userSettings.numberFormattingInfo

client.numberFormattingInfo

formatting._formattingData.numberFormatInfo

I would have hoped that I at least had the id for the user's currency to retrieve the exchange rate if it wasn't just simply supplied.

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @skoofy5 , 

 

I think you have a few issues.

1. To format the data you can use the formatting (the link below is for currency, but you have functions for all kind of data types): https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/formatting/format...

2. For each record you have the transactioncurrencyid field, which you can define for your dataset using property-set, so you know you have it provided in the dataset even if it's not defined in the view.

3. Currency sum is always a problem. Which currency is the right one? As you say, you can use the base for each record, and make the sum. Then you can use a request to "transactioncurrency" table (maybe linked to usersettings based on the field transactioncurrencyid), and get the rate and the symbol. Using the formatting from (1) you can show that value.

 

Hope this helps!

 

Kind regards,

Diana

 

Kind regards,
Diana
----------
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

I think you are looking for getGlobalContext.userSettings.transactionCurrency to get the current user's currency.

DianaBirkelbach
Most Valuable Professional
Most Valuable Professional

Hi @NickDewitt , 

 

The Xrm (and globalContext) shouldn't be used inside a PCF. Sometimes it works, but it's explictly specified in the sdk not to do it : https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/?WT.mc_id=BA-MVP-...


There are some userSettings properties for PCF, as @skoofy5 mentioned:

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/usersettings?WT.m...

but I don't see a transactioncurrency there.

 

Kind regards,

Diana

Kind regards,
Diana
----------
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

@DianaBirkelbach ah yes good point, I wasn't thinking of the Xrm object but more by importing the ClientGlobalContext.js.aspx like you would for a standalone HTML resource, but it looks like they are deprecating that too.

 

There is a currencySymbol property on the PCF UserSettings.numberFormattingInfo object, it looks like that could be used with the Formatting.formatCurrency function but I do wonder how that is going to work for different currencies that use that same symbol.

You should be able to get the information you need by querying the usersettingscollection table and filtering for the current user by using the PCF context WebApi to query the data directly:

 

 

 

// get the user settings for this user
const results = await context.webAPI.retrieveMultipleRecords("usersettingscollection", `$select=_transactioncurrencyid_value&$filter=systemuserid eq ${context.userSettings.userId}`);

// there should only be one row as we filtered for systemuserid
const currencyId = results.entities[0]._transactioncurrencyid_value;

// get the details of the currency
const currency = await context.webAPI.retrieveRecord("transactioncurrency",currencyId,"$select=currencyname,currencysymbol,isocurrencycode,exchangerate")

returns :

{
    "currencyname": "US Dollar",
    "currencysymbol": "$",
    "isocurrencycode": "USD",
    "exchangerate": 1.4400000000,
}

 

That should get you what you are looking for without using something that is due to be deprecated. The exchange rate seems to be auto calculated from the base currency aswell if you want to use that.

 

skoofy5
Continued Contributor
Continued Contributor

Thanks for the comments guys. Pretty much confirmed what I've already ended up doing earlier today as the only path. I thought I'd let everyone know here if they're after a solution.

 

Below is the query to return both the user's currency preferences, if available, and the base currency. For this particular scenario I'm not interested in the records' currencies as they could potentially vary from one record to the other and so cannot be aggregated, but as Diana pointed out you can grab the currency related to a record if you wish.

<fetch>
  <entity name="usersettings" >
    <attribute name="systemuserid" />
    <filter>
      <condition attribute="systemuserid" operator="eq-userid" />
    </filter>
    <link-entity name="transactioncurrency" from="transactioncurrencyid" to="transactioncurrencyid" link-type="outer" alias="usercurrency" >
      <attribute name="currencysymbol" />
      <attribute name="currencyprecision" />
      <attribute name="isocurrencycode" />
      <attribute name="exchangerate" />
      <attribute name="currencyname" />
    </link-entity>
    <link-entity name="systemuser" from="systemuserid" to="systemuserid" link-type="outer" alias="user" >
      <attribute name="fullname" />
      <link-entity name="organization" from="organizationid" to="organizationid" link-type="outer" alias="userorg" >
        <attribute name="basecurrencyprecision" />
        <attribute name="basecurrencysymbol" />
        <attribute name="name" />
        <attribute name="basecurrencyid" />
      </link-entity>
    </link-entity>
  </entity>
</fetch>

 

So what I have from this is:

 

Base

  • Symbol
  • Precision

User

  • Symbol
  • Precision
  • Exchange Rate

You can then add the "base" (all currency fields have a calculated base field added) columns to the view, or use addColumn to ensure the field is in the dataset:

context.parameters.dataset.addColumn([currencyfield + '_base']);

 

Then I get the unformatted value of the column to do whatever aggregation/maths I need using the base amount, or by taking the value of the base field times by the user's exchange rate I retrieved earlier. In this case I want to be able to switch between the base and users currency.

 

Finally I pass out the formatted value.

context.formatting.formatCurrency(100, 2, $)

 

I was really hoping that somewhere in the dataset info this would have been available already considering what else is already there.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (724)