Comments
Just had to deal with a failed v10.0.17 update deployment caused by AxDB ending up in a Recovery state loop which it could not get out of because of AutoClose being enabled (wait over 2 hours to see it was going resolve on its own accord). Finally I ran the query (ALTER DATABASE [AxDB] SET AUTO_CLOSE OFF WITH NO_WAIT;) and it completed Recovery within a few minutes. I was then able to resume the failed deployment at step 20 in LCS.
There's really no good use case for for AxDB to default to AutoClose enabled.
This improvement to the duplicate detection popup obviously did not get included in the 2020 Wave 2 or in the 2021 Wave 1 upgrades. We do see improvements to the Merge popup, but this is useless if we can't use the duplicate detection popup. Our end users need to see different data than is available OOTB from Microsoft on the duplicate detection popup in order to determine whether or not the records are indeed duplicates.
When can we get this popup to be configurable to add more fields, so that end users can make sound decisions on duplicate detection and merging?
Additional guidance and thought: The solution for Attachments must contain the flexibility of linking to the attachment vs actually moving the attachments. I.e. the order number field vs the document no (along with some line numbers) so the attachment basically is re-linked or could have multiple links in an Attachment relation table.
We have to export the Features management list into excel and then import into a sharepoint list. Added metadata makes using the sharepoint list more manageable, but it takes a lot of manual effort. Would love a flow to export the Features list directly into a sharepoint list. Additional filtering in Feature management page would be beneficial to exporting as well.