Release 31.03.2025
· 2 min read
Updates for DYCE apps available for download via AppSource
DYCE Essentials 2025.3.1.0
Fixes
- Preparations for compatibility of several DYCE apps with Microsoft Subscription Billing
DYCE IT-Business Toolkit 2025.3.1.0
Fixes
- Preparations for compatibility with Microsoft Subscription Billing
DYCE Project Billing 2025.3.3.0
Fixes
- Invoices created via Project Order - Service Billing page no longer include time recordings that are not related to the invoice (IC250770).
- Time recordings could not be released in the Project Billing (approval) page (IC251147).
- Preparations for compatibility with Microsoft Subscription Billing
DYCE Subscription & Recurring Billing 2025.3.2.0
Fixes
- Contract Price Update no longer includes service commitments from closed contract lines (IC250618).
- The Bill-to Customer Price Group is considered when changing the End User (IC250699).
- The Contract Detail Overview report has been extended to support Bundles (IC242480).
- Preparations for compatibility with Microsoft Subscription Billing
DYCE Time Tracking
Usability
Fixes
- Creating new time recordings was temporarily not possible on mobile devices.
- If resources were assigned to project tasks in BC, the description of the project task was no longer displayed in the task list. Furthermore, time recording for these assignments was not possible.
- The data model of the webhooks in the Time Tracking Integration for Jira and Azure DevOps has been updated. Please also check the webhooks in Azure DevOps (Documentation) or Jira (Documentation) and reactivate them if necessary.
- In the Time Tracking Integration for Azure DevOps, unnecessary error messages were displayed that were not relevant for Time Tracking.
- Changes to work orders in Jira and DevOps resulted in the work order number being overwritten. The number is now retained.
- Performance optimisations for time tracking and full synchronisation.
DYCE Sync
Fixes
- In some localisations, times and weekdays in the BC working hour templates were not transferred correctly.
- The creation of work orders in BC now also takes place if values are missing in secondary tables (e.g. Area)