This would be very useful!
Do you feel this idea connects to your wish?: Display Model and branch in the TSF header | Thinkwise Community (thinkwisesoftware.com) I think this is a great idea as well. However my question/idea goes further than showing the breadcrumb ‘root’. I’d like to show a set variable that can be seen from where in the application 😀
Feel free to create an idea for this! I feel this idea would be slightly different from the earlier mentioned idea. Idea created 😁👍
With auto-edit enabled this automatic selection also seems drastically lower performance/speed of the UI🤔
I’m curious about this too. Selecting a column in the main table doesn’t seem to help 👀
That’s great to hear! I’m just wondering how this didn’t get noticed during testing 🙂
IIRC, What we do is set the translation of the header to a single space: ‘ ‘. This way it shows no header but you still have the possibility to sort, filter etc. Haha that’s exactly what we do! However, the empty header takes up a lot of space so if it can be disabled that would be great 😄
I just had to go through a lot of validations, including the subnames. I found that some names in prefilters and tasks were created using a capital letter. However, I then bump into this same issue/bug where the SF offers me the option to change the name but it won’t allow me to change it since it doesn’t recognize capital letters.The workaround is very tedious (especially when having to rename multiple names): rename it to something else and then rename it to the same name without the capital letter.
This would greatly enhance the user experience 😄It’s also a bit inconsistent that week numbers can be shown in the scheduler, but not the date picker. This is actually something that is needed for our client in the agricultural sector 👀
After careful consideration we have decided to close this idea, as it has limited added functional value compared to using expression fields. I prefer not to pollute my data model with expression fields, especially when that expression fields sole purpose would be for a conditional layout. To me it makes more sense to place this expression in the conditional layout instead of the table.
I'd like to add to this topic with a few questions about DevExpress within Thinkwise instead of opening a new one: Is there an internal document or guide that Thinkwise uses for DevExpress best practic... I’d like to see official subreport support too, since the current workaround via Indicium is not something I’d like to use since it’s horrible to maintain. 😅
If the user would be in several user groups that in your case would all have difference configurations, which should be the leading configuration? Or should it be a more of a configuration that is derived from all configurations combined? Thanks for the quick reply 🙂 I’d expect the configuration to be combined if multiple user groups are assigned to the same user. Though thinking about it, instead of having these grouped options I think it would be better to be able to turn certain things on/off (For example turn on Prefilter creation and turn off screentype selection).I’ll create an idea for this 👍
Anything changed in the last 3 years? I’d like this feature
In January I posted a ticket (8441S) on TCP about this bug. The current status is ‘on the backlog’.So they are aware of the bug but a fix is not planned yet 🙂
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.