STATE REPORTING ISSUES
NOTE :: Various file formats are used on this page that may require download. If larger than 1mb, it will take longer to download. For instructions or more information, please visit our download page.
LAST UPDATED: NOVEMBER 26, 2013
Number of Known Issue(s): 3
|Nov 26, 2013||Some users may have received instruction to change a student's R1 reentry code to an E1 initial entry code and note the R1 in the comment section for the purpose of clearing the R1 fatal error created when running your Principals Monthly Report. This is not a process authorized by NCDPI.||Pearson is working to resolve the issues surrounding the fatal error in PowerSchool and until that happens, attendance codes should not be altered for the sake of clearing an exception unless the change is a true occurrence. If you have questions, please contact Ozella Wiggins at email@example.com.||TBA|
|Nov 21, 2013||After the State Reporting Release 22.214.171.124.0 was implemented during the Nov. 15 weekend work, QA performed regression testing to determine what issues remain with PMR. * Here are the findings: * 1. PMR 18 -- PMR is not reporting the student's original entry code for this school year when enrollment code is R5 or R6. * 2. Withdrawals are showing on all PMRs regardless of the month that the student withdraws. However, the ADM/ADA appears to be correct. This causes enrollment numbers to show an artificial increase in the withdrawals being reported here. * 3. PMR 5, 6, 7, 10 and 25 are reflecting track school information incorrectly. * 4. PMR 23 is incorrectly reporting 10-digit student numbers as invalid. * 5. R1 is not reporting the student's original grade level and code. * 6. Some totals are not correct on the PMR Summary report. * 7. Some sites are still unable to run a PMR because of incorrect data. * 8. NCDPI is working with Pearson to develop scripts to help correct: a) LEAs' inability to correct a student's re-enrollment history after the student is transferred to another school due to school ID being lost upon transfer. b) Bad Data generated by PowerSchool that causes RPG errors to show on the PMR exceptions. * 9. Pearson is researching a bug with the Core product that affects transferring students. Data gets dropped (e.g., school code, admission status). Please be reminded that the PMR Summary will be inaccurate until all FATALs are corrected.||No. 1 will be corrected in the Dec. maintenance release. Pearson will add a view so LEAs can see the R5 and R6 students.
Nos. 2, 3, 4, 5, 6 will be corrected in the Dec. maintenance release.
No. 7 also will be corrected in the Dec. maintenance release. This issue is related to one or more students with two or more enrollment records with the exact same entry and exit dates.
No. 8b: The bug has been corrected; however, Pearson needs to run a script to correct the bad data.
Due to the continued issues with the PMR, if any LEA has already run and approved their PMR for Month 1 and believe their information to be incorrect, they may un-approve, re-run the PMR, and re-approve their Month 1 PMR once the information is correct. LEAs may refer to the document 'PMR Validation Errors' -- the link shown -- as a reference for all Exception Codes and their severity.
If you have questions or concerns pertaining to your PMR, please contact the Home Base Support Center at firstname.lastname@example.org
|PMR Validation Errors|
|Majority of items expected to be be corrected in the Dec. maintenance release.|
|Sep 18, 2013||State Compliance Reports Updates Needed||Updates going this weekend (09/21-22) are PMR/GRS, Dropout, SAR, AIG - Phase 1.||Sep 21, 2013 updates did occur in maintenance weekend but problems still exist. Completion date TBD.|