Hi Anne, Great to hear that the problem is resolved in 2023.2. Unfortunately we are hindered with upgrading to that version until we have replaced the Mobile GUI with the Universal GUI. Would it be possible to hotfix this in our 2023.1 SF?
Hi Anne,Thank you for your answer. I am aware of how the deployer is able to execute incremental upgrades. The point of this idea was to let the SF generate the incremental upgrade scripts without having to archive the individual deployment packages manually.
Hi @Robbert van Tongeren, You stated: “The user who makes changes is not by default logged. This can however be found by looking at the update users on the current record.”. However, for deleted records this doesn't work because deleting only changes the tsf_valid_to of the last state of the record (which shows the last updated user, not the user who deleted the record). Did you by any chance also thought of a solution for this without having to create an instead-of-trigger on delete which first updates and then deletes the record for each system-versioned table?
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.
