I use the solution, suggested by Anne, quite often, but I still think the option to set persisted as an option is preferable as it is a property of the calculated column and not part of the calculation/expression itself. Upvote.
I think using Quality as a menu group for this screen is still the best location. Using sub names prevent typos and inconsistencies in using sub names. Therefore, it improves the quality of your model. Using a separate screen sound like a great idea to me. I totally agree.
I would like to bring to attention my Idea: https://community.thinkwisesoftware.com/ideas/reference-without-index-3648
@Boudewijn This means that the script / job does the cleaning? The problem is I think that after each upgrade the indexes will be present again (slowing down performance), and after a while dropped again. I still think it is better to do this manually. Another example is functionality which is only used once per year, then it could be that indexes automatically are dropped when they shouldn't be dropped.
Hi Peter, We have transferred you to our new ticket system. The old issue system will be available for you (read only). Please add a ticket in our Ticket Management System (TMS). This will be available in the same TCP portal.
It would be even better to be able to “share” the saved filter expression with other users or group.
I recently had the same problem: vote = vote + 1
Another sidenote: If you want to use this filling the trace columns automatically when inserting a record in the GUI then it is [u]not[/u] going to work since the GUI fills in [b]null[/b] values for each field which has not been filled by the user. This means that in your example the insert_user and insert_date_time columns will have null values instead of the username and the current date. The default value will only be set when no value has been given. If you set the columns to mandatory (not null) then the GUI will show an error because it passes a null value since the (data) model does not allow nulls. This could be fixed when the GUI also allows to pass [b]default[/b] as a value when a column has not been filled by the user. For example: I created a table called test_tab which has a column insert_date_time. On the database I manually set the default value to getdate() (as in your example). When I insert a record within my Windows GUI the debugger says it executes the followin
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.