Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties
labeljirareport


Date

 

Issues

Jira Legacy
serverSSDT JIRA
jqlQueryproject = INV AND fixVersion = v1.23.0
counttrue
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca



Summary

This release of the SSDT Inventory application contains the following bug fixes and improvements as detailed below.

Improvements

  • A Mass Load option for non-migrating districts is now available.  The "Migration Import" option is restricted to the ADMIN role and is located under the System menu.  This option will allow districts starting on Inventory to import data without the fiscal year restrictions, allowing prior year data to be imported into the correct fiscal year. 
    • This import will allow you to upload a csv of acquisitions, items or dispositions.  You can create your own csv or use the grid export from another instance.  
      • Note: if you do use an export from another instance, you will need to remove the id column from the csv file.
    • The "Inventory Item" import option will also create any code object that does not exist.
    • Districts can choose to optionally create the acquisition when the item is created, however this will happen for all items being imported.  Separate imports (files) should be used, one for items they want acquisitions created for automatically and one for items they do not want acquisitions created for automatically.
    • The data formats and headers for this option are the same as documented in the System→ Importer chapter found here: https://wiki.ssdt-ohio.org/x/fQK_Bw
    • If you are setting up a new district and not running the importer importing the Classic extract files, but choosing to use this new feature, you'll also need to make sure you complete it is assumed you have already completed the following PRIOR TO importing data:
      • Core→
      • System→
        • Capitalization Criteria: if the GAAP flag is checked the capitalization criteria will need to be completed.
        • Configuration: if you plan to use ADS you'll need to set this up.
        • Users: create user accounts for those that need to have access to the application.
      • USAS Integration will need to be completed.  See the Application Setup information in the Post Import Procedures for details.
  • Created a new Depreciation Posting Report.  This report replicates the Classic EISDEP report and includes both capitalized and non-capitalized items and is sorted by fund.

All updates for this release

Jira Legacy
serverSSDT JIRA
columnIdsissuekey,summary,issuetype,status,resolution
columnskey,summary,type,status,resolution
maximumIssues1000
jqlQueryproject = INV AND fixVersion = v1.23.0
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca