...
- Dispositions: Fixed the bug that prevented the filtering of the items when creating a Disposition. Users should now be able to filter by an active inventory tag when creating a disposition.
- FTD depreciation calculation was not handling negative depreciation properly. This has been fixed.
- Migration Import: Corrected the item import to provide a warning for invalid line length. The warning will display a Runtime Exception and will include a message that reads "Import size too short". This error will help detect import files that have wrapping problems.
- Items: Updated the item tag number to always be capitalized uppercase to prevent duplicate tag numbers from being created. Any existing duplicate tag numbers that only differ due to upper/lower case will need to be manually modified on the item record.
- Configuration: When closing the fiscal year, the "last closed fiscal year" field will now be updated in the Inventory Configuration.
- Items: Corrected the bug so that now once a new item has been added, users will be able to immediately edit the newly created item in the existing window.
- Updates made to the Fixed Asset by Source report include:
- Donation amounts, even if they do not have an associated acquisition, are now included
- Acquisitions that do not have an account code (the amounts are now included)
- The summary version of the Schedule of Change in Fixed Assets report by Fund was corrected (resurfaced from 1.18 release) and will now generate properly again.
- Migration Import: (Hot Fix) The importer was not calculating FTD depreciation correctly due to an issue on the 1.20 release. It was causing balancing issues involving the FTD depreciation amount when trying to balance 102, 104 and 305 Classic reports to their respective Redesign reports. It was causing negative depreciation amounts for items that were already fully depreciated and also overinflating FTD depreciation on other items causing the FTD depreciation to be much higher in the Redesign reports when compared to the Classic 305.
- Please note, if you performed a migration import using the 1.20.0 release (July 16-28th), you will need to re-import your classic data and then re-run your reports to balance. Note: The dates provided are based on the assumption that the releases are installed as soon as they are made available. If your ITC does not install the new releases when they become available, those dates may not apply to you.
...