Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

479 Ideas

HugoApprentice

The option to use IN as filter in the form listCompleted

The last couple of days we receive multiple questions from our end users that the standard form list in the GUI doesn't give the option to use ‘IN’ to filter results. We are very curious why there is no option to put multiple different values comma separated in the standard GUI filter?This group of around 25 end users just moved from a 20+ years old ERP system to our Thinkwise ERP system but they showed us how they worked in the old system and to be honest, it looks easy to implement in the Thinkwise GUI and we actually are a bit curious why nobody seemed to noticed this ‘gap’ before. Maybe we overlooked something but it seems that it can't be done in the GUI in the current version (2023.1.12.0).Not sure how to call the standard filter in the GUI, but in SF they call this filter a form list. In blue there are the options to choose from, they look like this in our Dutch version of the GUI: We miss ‘IN’ as option in this listWhat we need is the option ‘IN’ and a possibility to fill in the values comma separated. For example if you want to see details from 3 different orders 123, 567 and 999 in the old ERP system we would easily filter like this:Filter 3 different sales orders in the >20 years old ERP systemAs a select query this would result in something like:Select details from sales_orders where sales_order_id in (123,567,999)So nothing really difficult about this, so we hope you can put this very soon as a filter option in the GUI?In our old system the filter can also be built like this (see also the different options like ‘and’ and ‘ or’ on the left side as well):Ways to build a selection filter in the >20 year old ERP systemWe read in some other posts on the community about using AND or OR as a prefilter, so maybe this last picture can be helpful. Nevertheless for us the most important thing is to give our end users the possibility to just fill in multiple values comma separated. Maybe this is already possible, if so, hopefully somebody can explain how and if not, we hope Thinkwise can provide this awesome option very soon. Thank you in advance!

Robert Jan de Nie
Thinkwise blogger
Robert Jan de NieThinkwise blogger

Make Software Factory metadata available to AI so I can generate SQL templates from my IDECompleted

I want to use generative AI to draft the bulk of my SQL templates, directly from my own IDE (e.g., VS Code) together with tools like GitHub Copilot. For this to work reliably, the AI needs first-class context from the Thinkwise Software Factory (SF): the application’s model metadata and relevant UI information. The SF already maintains a rich, structured model of tables, columns, and references; exposing that to the AI is the missing piece.Why this metadata is essential for AI-assisted SQL When the AI understands my model, its output stops being generic and becomes project-specific:Tables, columns, PK/FKs – enable correct JOINs, WHERE clauses, and integrity-awareness. The SF’s data model explicitly defines these entities and relations, which the AI can use to pick the right join keys, respect cardinalities, and avoid hallucinated columns. Domains (user-defined data types) – domains act as abstract data types that drive constraints and UI defaults. Sharing domains helps the AI choose correct data types, casts, default values, and validation logic in generated SQL. UI semantics – properties like control type or visibility can guide the AI to prefer filtered queries (e.g., hide inactive rows by default) or to shape parameter prompts and WHERE clauses that match what end-users actually see. Template description & intent – short, descriptive text per template (purpose, invariants, edge cases) gives the AI the business intent it needs to generate more accurate and consistent code.How I propose to make this work Expose a compact model export for use in VS Code MVP scope: tables, columns (incl. nullability), primary keys, foreign keys, domains (name, base type, constraints). Optional scope: UI hints (visibility, control), default filters, and template descriptions. Delivery options (any of these would work): Indicium OData endpoint that surfaces a read-only view of the SF model (Indicium already provides an open API and can expose SF branches when configured). CLI/export task that writes JSON files into a repository (consumed by VS Code). VS Code extension that authenticates to the endpoint and injects the model as inline context for Copilot prompts. Use the model export as AI context in the IDE In VS Code, I want to select a template and have the AI read the JSON/endpoint to generate the initial SQL ready for review and refinement. Expected resultsSpeed: AI drafts 70–90% of the SQL, I focus on edge cases. Quality: Consistent use of keys, domains, and defaults; fewer “missing join” or “wrong column” errors. Discoverability: As Thinkwise continues to add AI-powered features (e.g., model enrichments and support for storing LLM embeddings), a model-aware export aligns with that trajectory. Future fit: Community use cases already show value in combining Thinkwise models with LLMs (e.g., natural-language search using embeddings), reinforcing the need for structured model access.