Hi @Jeroen van den Belt ,This issue was urgent, and I also sought help through other channels. I've already received some tips to improve performance. My apologies for forgetting to mention it here and for closing/withdrawing the ticket. Best answer I got:“ The get_gui_elemnts can be a bit slower duo to an index issue in IAM or having to many old version in IAM. If you performaned a platform upgrade it could be that is previously was configured with a recompile and this recompile setting was lost during the platform upgrade.The 2nd query I do not know. Cannot help you there. Might be a something related to performance monitoring. “ Kind regards,Gosia
Thank you @Edo Spijker, good to know.
Hi @Renée Evertzen I help @avandervelden with this ticket and I checked all export-options but it didn't work; the column contain data so it cannot be empty. When I renamed the column, the export worked perfectly. I got default and layout error but export was OK. I checked it and we hide this date-column in the form for almost every row. Solution for now: I took the column name back to the origin and added in the layout statement @import_mode <> 2 -- export. Now we get the data in the export-file, but..Is this the correct working of the application? In the grid is this column read-only for the table variant that we’re using. Tested via SF on Windows GUI 2023.1.10.0Extended properties:CustomDateMask - dd-MM-yyyy CustomDateTimeMask - dd-MM-yyyy|HH:mm:ss CustomTimeMask - HH:mm DisableZoomIn - no FloatingDocumentSize - 1350x700 FormAlignmentOfNumbers - right HTM
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.
