Recently active topics

When pasting a value in a combo box, it selects the first value that partly matches the text. This is very annoying when you pasted the exact value that you want to enter. It forces you to manually scroll to the right record and select it or use the lookup window.If there is an exact match, it should prefer that over the first matching value.For example:  

I use dark mode in the Software Factory and SSMS. It’s great that since the Software Factory is available via the Univeral GUI, that it supports dark mode.However, the Debug Center is missing this feaute and is always in ‘light’ mode:It would be great if the Debug Center gets dark mode as well since it’s used a lot during development.Yours sincerely,My eyes

As discussed in topic:Also the users of my clients are requesting for more contrast between the selection and the non selected lines.It would be great if we can have some impact on this. A css solution is also acceptable, not ideal.

The parameterized translations is a great tool for making certain fields more understandable for the end-users of the application.Especially with the return of the HELP function in the Universal GUIwe have some great tools to ‘explain the application logic’ to the user. What would be great is when the form-tooltip would be separated from the grid-tooltip, allowing the form-tooltip to be parameterized. (Not showing an ‘ugly’ curly bracket translation in the grid).Why?Hoovering over a field would allow us to explain to the user how a certain value is filled in. Giving room to a explanation with the values of the current row.This would greatly improve the understanding of certain fields for our users, especially ones that are ‘filled in by the application’.It is a step closer to the application than reading a help page or documentation about it, and provides a ‘live’ explanation without having to ‘calculate’ it yourself.For example:We have a couple of fields in a sales order line:currency

Often there are situations where you want to show a different tab-variant as a detail tab based on a specific property of the selected row in the main grid. This is possible by making multiple references and let the context procedure only show the detail tab with the tab-variant based on the property value.When there are multiple detail tabs for the main subject, this has one major downside though: Normally the GUI remembers the activated detail tab when the user switches rows in the main grid. However when the context procedure switches the reference for a different tab-variant, it activates the first visible detail tab.This creates inconsequent behaviour for the user when switching rows in the main grid because sometimes it does keep the same detail tab activated and sometimes it doesn’t. From the user perspective, the different references to the same detail tab are the same thing.To improve the behaviour of cases when the activated detail tab becomes hidden by a context procedure, t

I would like to see the Model Insights window to be variable in size. We use very long names and can only see the first part of it.For example: 

When permissions are added to a role by a developer in a branch, there are 4 types of situations:The object is new for the branch and permission is added to a new role The object is new for the branch and permission is added to an existing role The object existed at the start of the branch and permission is added to a new role The object existed at the start of the branch and permission is added to an existing roleI consider the first 3 situations happy-flow use-cases in which no extra risk is involved because either the role is new or the object is new. The 4th situation is different because the developer has changed permissions of something that already existing without creating it. This is mostly done as an exception when ‘fixing’ permissions that were initially forgotten. The risk for this situation is bigger because maybe the object permission was not forgotten but deliberately left out for that role. Specially for column rights this could be the case. Also a developer who added a

In Release notes Thinkwise Platform 2026.1.11 | Thinkwise Community aggregations for groups were added. Unfortunately there is only an extended property to disable this for all subjects.Please make it possible to disable aggregations for groups on specific subjects.   

The subtitles for open documents are great (Release notes Thinkwise Platform 2026.2.12 | Thinkwise Community), however there are some exceptions where you want to use the subtitle of the active detail (one level down) instead of the document itself. Most menu items in the SF are a good example for this. For instance in the Functionality screen you don’t want to show the branch name as subtitle, but you want to show the control procedure name. I am guessing this is the reason the subtitles are currently disabled for the SF.Therefor I would like a setting on the subject (+variant) level so that you can mark that subject to use subtitles of the active detail instead of the subject itself.  

At the moment, there are no plans to create a Workspace Listener for Linux (source).It would be great to not be limited to Windows and have support for automatic opening of your IDE on Linux. Context:Automatic opening of local code files  For additional convenience, Windows users can install the new Thinkwise Workspace Listener. This tool automatically opens the selected code file in your preferred IDE when clicking on the pencil icon. The Workspace Listener is optional. Without it, you can still edit and synchronize code locally (provided you use a browser that supports the Filesystem API), but you will need to manually open the files in your IDE.    Browsers with File System Access API  Chrome & Edge  Browsers without File System Access API  Safari & Firefox  Windows  ✅ Automatic syncs  ✅ Automatic opening (using the Workspace Listener)  ❌ No automatic sync  ❌ No automatic opening    Local code editing requires manual copy/

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 th

When a finished branch gets merged to it's origin (non-reciprocal). It becomes finalized and, depending on selection, archived. Further merging into and from this branch is thereafter no longer possible. Yet, active development is still possible in a finalized branch (even after unarchiving). Wouldn't it make sense to completely lock development in a finalized branch as well? I have experienced a scenario where an unsuspecting developer was actively developing in a finalized branch (without knowing it was a finalized branch) and then find out way too late all of his work is for naught.

When deleting a row in the Software Factory, it currently shows the generic message:Usually you can see the selected row in the background, however, I’d like bit more assurance when deleting things in the Software Factory. It would be great if it showed for example (when deleting):Functionality: Are you sure you want to delete {control_proc_id} Branch: Are you sure you want to delete {branch_id} etc.

In the universal GUI opening (a lot of) documents can make the navigation panel cluttered and even push the menu out of sight: Some suggestions to improve this: Split the navigation panel in two panels with seperate vertical scroll-bars as soon as the number of open documents exceeds a certain treshold Add levels for detail-documents beneath open documents and collaps them the same as the menu tree with (automatic) collapsing and expanding Add context (part of the breadcrumb) to the title or mouse-over of detail-documents to prevent having to open a document to see wich one is the right one Another suggestion: An option to lock an open document, so that it is available the next time I login to the application

We would like to have the ability to show table tasks on a grid line. This is especially useful for the mobile GUI and when just a couple of table tasks are available. Currently you can show tasks on the top or bottom of a grid in mobile. To start a task for a specific record you should select a line first and then select the concerning task. In the described case it is faster to select the task direct on the line. See print screens for further explanation. Task on top of grid (current situation) Example tasks on grid line

Hi Thinkwise community, We want to use the data type Hierarchyid. Hierarchyid is very useful for multi-level structures and is better for our performance. Now we use recursive methods but the bigger they get the slower they become and every time something changes you have to recalculate the entire tree.Unfortunately, this is not possible because the GUI does not support Hierarchyid. I saw a topic with a great solution by Anne Buit. Is it possible that Thinkwise can implemented this mapping? Thanks! Solution:“The hierarchyid is a type that does not have a direct mapping to any internal datatypes used by the technology of the GUI so a conversion must be made to a mappable type whenever this value is loaded into the memory of the GUi (e.g. to nvarchar(4000) and back to hierarchyid).” Topic:Support for System Data type - Hierarchyid

When I use a specific message and have it refer to a parameter with a lookup, it will show the “id” value instead of the “name” value of the lookup.Ex:translation of messageCurrent result:showing the “id” valueDesired result:using the actual “name” value of that parameterIt would be nice to have it use this “name” value, so I do not need to add another parameter to get the result I desire.

Having countless of program object types makes it kind of a pain for filtering when dealing with merge conflicts (especially merge sessions with numerous conflicts).  Long long list of object typesIn my instance I know a majority from the conflicts originate from Translations. Now I have to manually scroll all the way down to the ‘T’ area and still look around there. Would be nice if I could just type and search instead.

During development, we wish it would be possible to make table schema changes directly in the active development database from within the Software Factory. For example, adding, modifying, or removing table indexes without requiring a complete creation routine.This will significantly accelerate the development process. 

We use several scripts that we run manually on the SF database. One example is a script that suppresses all validation messages for a branch. We run this immediately after creating a feature branch, so that open validation messages carried over from the development branch don't obscure new messages originating from the feature branch itself.We have included this script in our model as a dynamic procedure, which means it falls directly under model maintenance. The procedure has been marked as inactive, because it should not run during every deploy — we only want to execute it manually.However, for inactive procedures the execute button is also disabled. This means we have to activate the procedure first, run it, and then deactivate it again. A bit cumbersome.Idea: allow the execute button to remain available for inactive dynamic procedures, so they can be run manually regardless of their active/inactive status.

Sometimes you apply filtering to a detail to get a certain result. Then you switch rows on the main list. And go to the same detail but the detail is still filtered on the previously used filtering so you don’t see any rows until you remove the previously used filtering. I find this very confusing please clear the filtering on a detail when the main row is switched.