Notifications
Announcements
Hello,
I have an table with custom currency fields, when I try to merge 2 entities of this table I get this error :
TransactionCurrencyId needs to be supplied to format the money field (Id: 666dd33d-e554-4afd-b8e7-77dd5de01da7, Name: ***, Value: 8107, Entity: lead).
Have someone any clue about it and how to solve it?
Thanks!
Hi @spaillasse
Text(<<SOME FIELD HERE>>,"[$-en-US]$#,###.00")
That should fix this.
------------------------------------------------------------------------------------------------------------------------------If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.If you like my response, please give it a Thumbs Up.
HI @SpongYe
I forgot to mention I'm using a model-driven app, I believe your solution is for a canvas app?
@spaillasse
Can you add the Currency field on the Lead form (or add the column on the view) and see if both records have a value for the currency lookup?
It is pretty likely that one of the Lead records was automatically created by a specific integration and the default currency value was not populated. In order to resolve that, a default currency lookup value must be populated in such integration to ensure that all Lead records have the value for it.
@LinnZawWinI added the currenty field on the form, one of the entity indeed had no value in it so I added my currency, but unfortunately I still have the error.
Besides, using the web API I can confirm the field "_transactioncurrencyid_value" as the same value for both records (see screenshot).
I can only see one record in the screenshot.
Based on the error message, the one missing the currency value is the lead entity with id = 666dd33d-e554-4afd-b8e7-77dd5de01da7. So, can you please double check the "_transactioncurrencyid_value" of the record with that ID via Web API?
Nop, the id 666* is the guid of the field, not the record. The ids of both records are 7a208d9a-7a96-ed11-aad1-000d3adf7052 and f025ab63-366f-ed11-9561-000d3adf7052. Both have the same
This seems to be the result of a recent change to the merge logic - I've written up some details on my blog, along with a workaround for when you're using the standard merge screen.
Big thanks @MarkData8 for this information!
How did you know Microsoft had changed the merge logic? By chance, do you have any link to a Microsoft resource on which they communicate about that?
There's no official documentation that I've found, only observing the behaviour which used to work and now generates this error for the same request.
Ok I read the article on the blog, thanks so much!
Unfortunately, even with unticking the "View fields with conflicting data" option, I still cannot see the "Currency" field in the list to be merged, don't understand why, strange because the field exists on the entity (see screenshot).
Edit : ok I managed to merge using the web api by adding manually the field in the body payload:
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
In our never-ending quest to improve we are simplifying the forum hierarchy…
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Kalathiya 445
WarrenBelz 386 Most Valuable Professional
MS.Ragavendar 321 Super User 2025 Season 2
