After upgrading he SF from 2022.1 tot 2023.1, an existing model (± 5 years of development), is giving the following error: The error, stating ‘Unique index is equal to the full primary key’The consequence, according to the SF is the following: The consequence of this error, stating ‘Foreign key constraints may introduce dependencies on this unique index, causing it to become difficult to delete or re-apply. This will also result in errors during full code execution’However, when going through all the steps of creation, no errors occur.The solution, according to the SF:The solution of this error, stating that ‘Changing the index columns to not be equal tot he full primary key or delete the index’Since this was fine in version 2022.1, it is unclear what to do here.This was developed in collaboration with the professional services of Thinkwise. The usage if mainly for primary keys that include a date. All these indexes have the extension _unieke_datum (_unique_date but in Dutch). The exac
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.
