Migration to new agent: SQL segments no longer active

Feature(s) impacted

Smart segments defined on the old agent via a SQL query.

Observed behavior

Filtering no longer takes place on the collection despite the request being shown.

Expected behavior

Segments should continue to work as migrating them was not explicitly indicated.

Failure Logs

From what I understand in this post, this is expected:

This was a disagreeable surprise as I tried to follow the docs carefully.
Smart Segments | Node.js Developer Guide (forestadmin.com)
This page says nothing about segments defined from the UI. It is the only page that mentions segments on code migrations.

I fail to see how I could have known this before running the migration and realizing that my segments are broken. Did I miss some documentation somewhere?

If not, please add a page on Code transformations | Node.js Developer Guide (forestadmin.com) for future users to be aware that this has to be done.


  • Agent technology: nodejs
  • Agent (forest package) name & version: 1.40.1 with sequelize 6.37.3 and sequelize-typescript 2.1.6
  • Database type: MSSQL
  • Recent changes made on your end if any: Migrating from old agent.

Hello @kll,

Thanks for the report, as you’ve seen from the other post, the @forestadmin/agent does not allow the creation of SQL segments via the UI.

It should have been added to the list of missing features in the Migration guide. Sorry for the inconvenience this has caused.

I’ll update the page to reflect this.

Best regards,

1 Like

Thanks for the quick reply! In the meantime I did port all my segments through code so it’s not a huge deal, I just wish I knew before discovering it in prod :stuck_out_tongue:

For sure, it’s not always a good thing to discover surprises after the migration has started ! :face_with_open_eyes_and_hand_over_mouth:

The documentation with the updated section is live :slight_smile:

1 Like