Follow up on Heatmap Bug with Multi-Currency Watchlist

Follow up on Heatmap Bug with Multi-Currency Watchlist

[Ammar Faizi]

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

Re:Follow up on Heatmap Bug with Multi-Currency Watchlist

[Vignesh Kumar Nadar (BLOOMBERG/ 731 LEX)]

[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]

Hi Ammar

It was great talking to you at the user interview yesterday.Thanks for flagging and sharing detailed reproduction steps along with JSON payload.
This is very helpful.
In the meantime, we'll keep you posted as we investigate further and let you know
once we have a fix.

Best,
Vignesh

From: ammarfaizi2@gnuweeb.org At: 08/18/25 13:08:27 UTC-4:00To:  Vignesh Kumar Nadar (BLOOMBERG/ 731 LEX ) ,  Emma Demers (BLOOMBERG/ NEWSROOM/ ) ,  Srishti Sharma (BLOOMBERG/ 731 LEX ) 
Cc:  Tanya Kureishi (BLOOMBERG/ NEWSROOM/ ) ,  Serena Chang (BLOOMBERG/ 731 LEX ) ,  alviro.iskandar@gnuweeb.org,  gwml@vger.gnuweeb.org
Subject: Follow up on Heatmap Bug with Multi-Currency Watchlist

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/36DBC7EAF256426ABFB0F8F8D21
B2A98

{
    "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



[-- Attachment #2: Type: text/html, Size: 5385 bytes --]

Re: Follow up on Heatmap Bug with Multi-Currency Watchlist

[Alviro Iskandar Setiawan]

On Tue, Aug 19, 2025 at 12:08 AM Ammar Faizi wrote:
> 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.

BTW, a temporary solution for this, instead of using USDIDR:CUR, use
USD:CUR. So the adjusted trades will be:

  - Buy 1 XETUSD:CUR at 4K USD.
  - Buy 1 XBTUSD:CUR at 116K USD.
  - Buy 100 USD:CUR at 1 USD.

You can't track your rupiah to US dollar changes though, but at least
it shows the correct heatmap tiles when you have USD in your holding.

I suggest using that temporarily until the Bloomberg Engineering team
fixes the multicurrency issue.

tq
-- 
Software Engineer & ITPM Officer
Alviro Iskandar Setiawan

Re: Follow up on Heatmap Bug with Multi-Currency Watchlist

[Ammar Faizi]

On Thu, Aug 21, 2025 at 04:34:27AM +0700, Alviro Iskandar Setiawan wrote:
> BTW, a temporary solution for this, instead of using USDIDR:CUR, use
> USD:CUR. So the adjusted trades will be:
> 
>   - Buy 1 XETUSD:CUR at 4K USD.
>   - Buy 1 XBTUSD:CUR at 116K USD.
>   - Buy 100 USD:CUR at 1 USD.
> 
> You can't track your rupiah to US dollar changes though, but at least
> it shows the correct heatmap tiles when you have USD in your holding.
> 
> I suggest using that temporarily until the Bloomberg Engineering team
> fixes the multicurrency issue.

Oh, nice. It works. I'll use that temporarily.

Thanks.

-- 
Ammar Faizi