Follow up on Heatmap Bug with Multi-Currency Watchlist

[Ammar Faizi <ammarfaizi2@gnuweeb.org>]

Hi Vignesh, Emma, Srishti,

It was nice to meet you guys. Thanks for the Zoom meeting.

This is the follow up on the heatmap bug.

The bug occurs when a watchlist includes assets priced in different
currencies. Below is a step-by-step reproduction of the bug:

1) Create a new watchlist with USD as the base currency.

2) Add the following trades:

  - Buy 1 Ethereum (XETUSD:CUR) at price 4,000 USD.
  - Buy 1 Bitcoin (XBTUSD:CUR) at price 116,000 USD.
  - Buy 100 USD (USDIDR:CUR) at price 16,000 IDR (Indonesian Rupiah).

In this scenario, Bitcoin should be my largest holding in USD terms.
However, the heatmap incorrectly displays USDIDR as the largest holding,
despite its value being only 100 USD.

I think a heatmap tile is now calculated by multiplying the number
of shares with the current price without caring about the currency
difference. That's probably the problematic part.

For now, the heatmap feature in the watchlist section completely messes
my visual up and not much useful because of this bug.

To be more specific for the Engineering team, I've included a JSON
payload for the watchlist creation endpoint:

HTTP POST
https://login.bloomberg.com/watchlist-service/create/36DBC7EAF256426ABFB0F8F8D21B2A98

{
    "portMeta": {
        "name": "ABC",
        "currency": "USD",
        "isDefault": false
    },
    "holdings": [
        {
            "security": "XETUSD:CUR",
            "buydate": 1755534614182,
            "shares": 1,
            "buyprice": 4000,
            "torder": 0
        },
        {
            "security": "XBTUSD:CUR",
            "buydate": 1755534575189,
            "shares": 1,
            "buyprice": 116000,
            "torder": 1
        },
        {
            "security": "USDIDR:CUR",
            "buydate": 1755534551554,
            "shares": 100,
            "buyprice": 16000,
            "torder": 2
        }
    ]
}

Let me know if you need further details to resolve this issue.

Thank you!

Best regards,
-- 
Ammar Faizi