If you always want to print the same columns you could make a variant of the list with the columns you need. OR You could use the export functionality to achieve this. You can hit Export or even select the rows first you'd like to export and then it Export. Then Hit Advanced Options [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/56bafce4-c68f-40d3-86fb-bc4314ad9ab3.jpg[/img] Is this what you were looking for?
[quote=Robert Jan de Nie]I think that editing versions that are not 'in-development' should be prevented at all times. There is usualy no reason a developer should want to change past versions. The only situation I can think of is applying a hotfix to an older version or something. But this is the exception, not the rule. If you want to do that, you can easily change the status of the old version to 'in-development' for a few minutes and then apply the change.[/quote] I [b]strongly agree[/b] with Robert Jan. Instead of making your version go red (sometimes it will, sometimes it wont) or giving a message, I rather not be able to change anything in project versions other than "In development"; but I could agree if some other statusses should not become read-only, but those should be reviewed. Editing something in a previous, inactive, version is such a waste of time, and sadly it sometimes happens. :expressionless:
If you experience this problem, make sure to [b]NOT[/b] to set the next setting to "TRANSPARENT" (see screenshot) [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/eaf0c402-7ae8-482a-a65e-0048da192846.jpg[/img] The issue will be resolved in a newer version of the GUI
Internal reference: 68125
Hey Anne, In this case its a RDP connection to Windows Server 2012 R2
I think both situations will have it pros and cons and I think we've identified those in our posts.
I think one way to achieve this is with prefilters. Another way to achieve this would be with views . I'd make a/some extra table(s) where you can determine which supplier can check which suppliers' orders and which users are with the supplier. Both ways (prefilter/views) could use this data model to 'filter' data. I think i'd choose views over prefilters, because you'll probably want to also change the rights for columns on the tables. Making views would make you be in control 100% of the data the suppliers can see. With prefilters you can risk the supplier sees too much information (columns, not rows).
It is not possible to set your own color schemes. You can choose from a variety of schemes in your user preferences (if enabled in IAM). Another 'idea' would be to change the transparency to 0%. See screenshot:[img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/4988d94e-7006-4294-867f-d35e8fe9a581.jpg[/img]
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.