InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Add a new idea Subscribe
Status Community Opportunity
Categories InterSystems IRIS
Created by Felix Vetter
Created on Sep 29, 2022

RELATED IDEAS

Use the built-in feature engineering in AutoML to transform datasets

The IRIS AutoML Provider includes feature engineering to clean and remodel data sets. It would be beneficial to use the first part of the AutoML provider separately to transform datasets. For e.g. analytics without using machine learning afterwards. Instead of the SQL statement "TRAIN MODEL" e.g. "TRANSFORM Example.Demo" to get back a transformed dataset for further work.

  • ADMIN RESPONSE
    Oct 31, 2025

    Thank you for submitting the idea. The status has been changed to "Community Opportunity".

    Stay tuned!

  • Post comment
  • Admin
    Vadim Aniskin
    Jun 23, 2023

    @Felix Vetter, you have a comment on your idea. Please answer to help your idea to be promoted.

    Reply
  • Thomas Dyar
    Jun 2, 2023

    Great idea, and we have thought we could expose the feature engineering in different ways, including a plugin capability to register code that could be run either before or after the feature engineering that IntegratedML does, so users could customize the process. I think for this, we may need the new syntax, or we could have a USING flag such that "TRAIN MODEL dontTrain FROM Example.Demo USING {'featureExtraction': 'mySchema.newTableName'}" and in that case ignore the model name and only do a "CREATE TABLE ... AS SELECT ..." . One caveat is that feature engineering sometimes results in a table for ML training that has more than the 999 column limit for SQL tables in IRIS, so in that case we would fail? Or have another using {'featureExtractionFileOutput':'/path/to/dataframe/output'}... ?

    1 reply