Saturday, July 6, 2024
3 changes
1 change
Resolved issues and error corrections
The appointment schedule now hides resources that are not linked to any appointment, preventing errors when users interact with the booking timeline. This keeps the resource booking view focused on relevant resources and avoids a traceback in normal scheduling workflows.
Original PR description
**How to reproduce:** - Make a new resource - Go to Schedule -> resource booking view (gantt by default) - Click on the timeline of newly created resource This gives a traceback. **Technical Reason:** - The case where resources has no appointment was not handled in the 'appointment_type_sync_duration.js' file. Handling this case with if statements. - The resources are displayed even though they are not attached to any of the appointment. Handling this by adding the domain. **After this PR:** - There will be no traceback on clicking the timeline of resources with no appointment (there will be no such resources due the domain). - Resources which are attached to atleast one of the appointments will only be displayed. Task-4000872
2 changes
Resolved issues and error corrections
Fixed a bug in the Partner Ledger report where the search filter was not functioning properly. Users can now successfully search and filter partner information using the search bar, improving the usability of the accounting reports feature.
Original PR description
Open partner ledger Filter using the search bar Issue: nothing occurs opw-4022937 opw-4035568 opw-4035471 opw-4034238 opw-4034165 opw-4032285 opw-4032408 opw-4027662 opw-4031833 opw-4028685 opw-4029858 opw-4029592 opw-4029202
This fix resolves an issue where not all invoice attachments were being included in the German DATEV CSV export file. Previously, some attachments were missing because the export process wasn't consistently handling all attached files, which could cause import failures in DATEV accounting software. The fix ensures all attachments are now properly included in the export.
Original PR description
Currently there is an inconsistent way of handling attachments for the datev export. In the documents.xml all files are included (based on _get_mail_thread_data_attachments) and in the csv export only attachments directly attached to the account.move are included. This will result in missing files when imported into datev because the BEDI-Reference is not included.