I think that's an ugly work-around. Performance-wise it's also better to prevent an unnecessary update trigger, just because the insert trace columns need to be filled. I still would like the feature to add a default constraint on a table column. Which should result in something like this (but then for the columns insert_user and insert_date_time):[img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/e35b9f3e-9f1a-455b-aec9-ec8355e0b7ed.png[/img] If the above possibilty is added we can remove the update on trace columns for the insert trigger and only keep the update in the update trigger.
The task 'Renumber columns' already exists under 'Data model' -> 'Columns'. (we are using SF 2018.3) [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/6e2b5d8f-ed03-4d05-be7b-481c110f06ed.png[/img]
There's a pretty negative side effect of using a subroutine ('procedure' type) within an instead of trigger. If applied to an instead of trigger a cursor or while loop will be necessary because the inserted table may contain multiple rows. This could have a great impact on the performance of the trigger. So I don't think it's the best solution. It's also possible to create a procedure with multiple templates and assign the necessary template to each view. The developer who has created the instead of trigger already copied the complete code of relation_address_view into the IOT template of person_look_up. But that does mean we have to maintain the exact same code in multiple places.
We did this because the iot (insert) of relation_address_view creates a new address and links it the relation. The iot (insert) of person_look_up view has to create a relation first before executing the same statements as the iot (insert) of relation_address_view. In the 'low code' mindset we would like to reuse the iot (insert) from the relation_address_view with the inserted values of person_look_up.
Hi Robbert, your solution works! We've created a procedure in TSF that includes every (scripted) assembly and assigned it to a 'Manual' code group (which is executed at the very end of every upgrade). [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/c0f71e5c-9c61-4466-9bf3-1f1330a79a26.png[/img]
We still want to allow sorting by users. So that's not an option. If we would create an index for every possible sort column in the table won't that slow down insert, update and delete actions? Because it means that every index needs to be updated after manipulating a record. In this case we have a valid argument to create the indexes for sorting because the table 'trade_item' will most of the time be used to look up information and not manipulate them.
That would be awesome! Just installed the newest Windows 10 update on my personal laptop and turning on 'dark mode' was the first thing I did after the update.
Hi Sharp, all available 'extended properties' are listed on: [url=https://office.thinkwisesoftware.com/docs/docs/sf/extended_properties.html#docsNav]https://office.thinkwisesoftware.com/docs/docs/sf/extended_properties.html#docsNav[/url]
Hi Sharp, there's an option in the runtime configuration to set the form alignment of numbers. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/6ab55fc2-61e0-454f-9613-ead37aba5420.png[/img] You can find/add this option under 'Runtime configuration' --> 'Extended properties'.
Hi Mark, it's already possible to open a tile item as a pop-up via 'Alt + Left-Click'. As far as I know this works for tile menu items, detail tiles and treeview menu items.
Hello Anne, thank you for your response! We actually have a license for UltraCompare, so it's the default diff/merge tool we use. I'll create a topic in the ideas section. ;)
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.