bizarre bug on screener for past date when 2 or more aggregate functions are used

Hi P123,

When using 2 or more aggregate functions in a screen and for a date in the past more than ~1 or 2 weeks ago → display NA for some of the original factors.

This is not only a display bug as it seems to also create issues for my calculations in a more complex screen.

I can share the more complex screen later but if you can first have a look at this, it might fix all the problems in one go.

See attached screenshot with link to public screen.
https://www.portfolio123.com/app/screen/summary/247753?st=1&mt=1

You can play with it by

  1. changing the date (it works with today’s date but not when the date is more than 1 or 2 weeks old)
  2. turning on/off 1 or 2 aggregate()

Thank you,

Jerome


Bug past date with 2 aggregates in screener.pdf (216 KB)

That’s the data limitations with historical screens imposed by data provider. Columns become NA after a certain number

Hi Marco,

No - this is not it in this case. There are only 40 stocks displayed on the screen courtesy of the last row “RBICS(leisure)”

→ And it would be the same problem whether I have 2 rows of aggregate calculations or one
→ and it would not work either when I use today’s date (shift the date to today and everything works fine)

can you please have another look at it?

J

I’m not able to reproduce this. I ran it a number of times on different dates and didn’t get any N/As.

Uh? I just reran the screen per the link above and still have the same problem.
Right hand column, screenshot attached → N/A only for BetaInd.

Did you

  1. Make sure that both Aggregate rows were active?
  2. Choose the date 10/01/2020 (01 Oct 2020) for example

Thank you,

Jerome


Hi Jerome. We were able to replicate the issue and we are looking into it.

Jerome, it’s a different restriction. Historically there’s a limit with rows & # of columns. After a certain number of columns all values are NA. Try re-ordering the rules and you will see a different column become NA.

Yuval cannot reproduce bc he has an admin account

Thank you Marco.

  1. To be safe, can you confirm that this is just a display thing i.e. the values that I store in @variable are correctly retrieved, stored and used?

In other words, when I use Showvar(@x, some function using P123 data)…
→ the column of P123 data might display N/A
→ but the variable @x would have stored and used the correct value.

For example, see this public screen where I was playing around with calculating the beta5Y of stocks based on {industry ; yield yes/no ; Debt to Equity ratio} → https://www.portfolio123.com/app/screen/summary/247744?st=0&mt=1

  1. I had a lot of N/A on my calculated Beta “@MyStockBeta” in this screen which is what attracted my attention.

However, it looks like the N/A are due to TxRate%() which seems to be missing quite a few historical data points.
Thoughts?

Thank you,

Jerome