added

June 2023 update

This month's release includes customizable y-axes for charts, easy Excel downloads of chart data from dashboards. We've also made improvements to better represent Visible Alpha consensus revisions, update Data Explorer with new data immediately, and resolved various bugs.

New features

  • Charts: Allow customization of y-axes under chart settings. The min/max, decimal places, units (percent / percentage points), and suffixing (millions / billions / etc) are now customizable.
  • Charts: New "download data" action under the Download button, which downloads chart data as an Excel file. This is available in both Signal Explorer & on dashboard chart widgets.
  • Dashboards: New charts may now be added to dashboards (previously, it was only possible to add existing charts from the Library).

Improvements

  • Visible Alpha data: Now set the Exabel "known time" of each data point to be the Visible Alpha "revision date", which is the date on which brokers publish their estimates. This ensures that Exabel represents Visible Alpha data exactly as presented in their terminal. Previously, the Exabel "known time" was set as the publish time on the Visible Alpha feed. However, this introduced data issues when Visible Alpha restate / correct their data, such that the publish time no longer reflects when the broker estimates were actually revised.
  • Data Explorer: updates to a data set now appear immediately in Data Explorer. (An exception is for deletion of data - this will only show up with a lag of about 12 hours.)
  • DSL: The Visible Alpha functions va_actual(), va_consensus(), va_metric() and va_revisions() functions can now be evaluated for Visible Alpha company-line item entities, in addition to companies. When evaluating the signals for company-line items, the parameter (line item ID) should not be specified.
  • DSL: The company_calendar() function now supports the extend parameter combined with alignment='rd', which means that it can produce future report dates. (Previously extend could only be used with the fp and afp alignments.)
  • DSL: The publication_date() signal and the report_date() functions get two new parameters freq and extend, which have the same semantics as with company_calendar().
    • freq can have the values FQ/FS (default), FQ, FS and FY.
    • extend can be a Boolean or an integer and can be used to limit the number of future dates returned. In order to make this a backwards-compatible change, the default value is True (whereas it is False for company_calendar()).
  • Prediction models: Don't include the baseline prediction in the trained model when using the "Optimize for high-value alternative data" setting. This ensures that the model uses the user's alternative data.
  • Dashboards: Hide widget filter/settings toolbar by default; and display selected companies / entities in chart widgets when they are part of a group of widgets.
  • Dashboards: Streamlined interface for displaying errors on table widgets.
  • Charts: Date range selector becomes more compact when there is limited space; this applies to both Signal Explorer and on dashboards.
  • Charts: Display actual values (rather than percentages) in tooltips on pie charts.
  • Design: Tweak scrollbar appearance to make it more visible.

Deprecations

  • DSL: Deprecated the period parameter in publication_date() and report_date(). This has been replaced by the freq parameter, for consistency across functions.

Bug fixes

  • Prediction models: Fixed bug where the next prediction was not being displayed on models that predict a global signal.
  • Prediction models: Correctly reset the "Optimize for high-value alternative data" setting when toggling to custom configuration. For models that may be impacted by this, we recommend to switch between "Automatic modeling" and "Custom configuration" once and save, to correctly reset the option.
  • Dashboards: Fixed missing Bloomberg tickers when creating a table with a list of companies (rather than a tag).
  • Signal explorer: Fixed an issue where dates were displayed erroneosly on the DST start date in time zones with greater time zone offset from UTC than the time of day for the DST change.
  • Alerts: Correctly populate feed & alert filters with data set alerts when navigating directly to the feed page.