District Administration

User Tools

Site Tools

Trace: • ASCENDER DataConnect (ADC): Level 1 Errors Guide
academy:adc_l1errors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
academy:adc_l1errors [2026/08/27 16:06] – lcamarilloacademy:adc_l1errors [2026/09/08 14:28] (current) – lcamarillo
Line 1: Line 1:
-======ASCENDER DataConnect (ADC): Level 1 Errors ======+======ASCENDER DataConnect (ADC): Level 1 Errors Guide======
  
 <WRAP box #no-print>{{:images:printer2.jpg|printer icon}}[[academy:adc_l1errors <WRAP box #no-print>{{:images:printer2.jpg|printer icon}}[[academy:adc_l1errors
Line 5: Line 5:
 </WRAP> </WRAP>
  
-**Created:** <color #ed1c24>In Progress</color>+**Created:** <color #ed1c24>08/27/2026</color>
 \\ \\
 **Reviewed:** <color #ed1c24>In Progress</color> **Reviewed:** <color #ed1c24>In Progress</color>
Line 15: Line 15:
  
  
-<WRAP round intro>This guide goes over how to best view the **Level 1 Errors** on the **ASCENDER DataConnect (ADC)** tool. +<WRAP round intro>Use this guide to review Level 1 Errors in the ASCENDER DataConnect (ADC) tool. Level 1 Errors identify data that could not be successfully published to the Operational Data Store (ODS).
 </WRAP> </WRAP>
  
Line 34: Line 34:
 VCV Keep both tabs open.\\ VCV Keep both tabs open.\\
  
-<WRAP box>**NOTE**: Keeping both **ASCENDER Enterprise** and **ASCENDER DataConnect** open allows users to easily navigate between two application and helps prevent dashboard timeout issues.</WRAP>+<WRAP box>**NOTE**: Keeping both **ASCENDER Enterprise** and **ASCENDER DataConnect** open allows users to easily navigate between the two applications and helps prevent dashboard timeout issues.</WRAP>
  
 ----- -----
Line 56: Line 56:
 VCV Scroll down to the **Domain & Entities** section. VCV Scroll down to the **Domain & Entities** section.
  
-Errors can be reviewed using either of the following methods:+Errors can be reviewed using either of the following 2 methods:
   * **Download the API Errors File (CSV)** to review the errors in a separate file.   * **Download the API Errors File (CSV)** to review the errors in a separate file.
   * **Review the errors on screen** by scrolling through the **Domains and Entities** section.   * **Review the errors on screen** by scrolling through the **Domains and Entities** section.
- 
-<WRAP center round info>When reviewing errors on screen, each entity is displayed along with its error status. 
-</WRAP> 
  
 ----- -----
Line 67: Line 64:
 ===== Reviewing Level 1 Errors ===== ===== Reviewing Level 1 Errors =====
  
-==== Download the API Errors File (CSV) ====+==== Method 1: Download the API Errors File (CSV) ====
  
 The **API Errors File (CSV)** provides a consolidated list of Level 1 Errors identified during the run.\\ The **API Errors File (CSV)** provides a consolidated list of Level 1 Errors identified during the run.\\
Line 75: Line 72:
 {{:general:adc_l1e_api2.png|Download the API Errors File}} {{:general:adc_l1e_api2.png|Download the API Errors File}}
  
-2. Open the CSV file. +2. Open the CSV file. The following formatting adjustments are recommended to improve readability:
- +
-The following formatting adjustments are recommended to improve readability:+
   * Expand the column widths as needed to display the contents of each column.   * Expand the column widths as needed to display the contents of each column.
   * Apply **Wrap Text** to columns **F** and **G** to display the complete error information within each cell.   * Apply **Wrap Text** to columns **F** and **G** to display the complete error information within each cell.
  
-==== Review the errors on screen  ====+==== Method 2: Review the errors on screen  ====
  
-**NOTE**: When reviewing errors on screen, each entity is displayed along with its error status.+<WRAP center round info>When reviewing errors on screen, each entity is displayed along with its error status. 
 +</WRAP>
  
 1. Click the **Number** in the **Error** column to view more details. 1. Click the **Number** in the **Error** column to view more details.
Line 90: Line 86:
  
  
-2. The entity expands, and under **Events and Errors** you’ll see the error description. Click **Expand JSON** to see what value was sent.+2. The entity expands, and under **Events and Errors** you will see the error description. Click **Expand JSON** to see what value was sent.
  
-{{:general:adc_l1errorsscreen2b.png|Reviewing Entity Level 1 Error Details}}+{{:general:adc_l1errorsscreen2.png|Reviewing Entity Level 1 Error Details}}
  
  
-3. This information, along with the error details, can be used to identify:+The information on the image below, along with the error details, can be used to identify:
   * The issue that requires correction.   * The issue that requires correction.
   * The staff member associated with the error.   * The staff member associated with the error.
  
-{{:general:adc_l1errorsscreen3a.png|Reviewing JSON Details}}+{{:general:adc_l1errorsscreen3a.png|Reviewing JSON Details}}\\ \\ 
 + 
 +<WRAP box>**NOTE**: Corrections must be made in the applicable **ASCENDER application** before submitting a new run. \\ \\ For example, if an employee's **Date of Birth** is incorrect, the information must be corrected in **Personnel** before sending a new run. 
 +</WRAP>
  
 ----- -----
  
-===== Fixing the Data ===== +===== Create New Run =====
- +
-Access the ASCENDER DataConnect (ADC) tool. +
- +
-{{:general:adc_create_new_run.png|ADC Create New Run}} +
- +
-1. From the Dashboard, click **Create New Run**. The Create Run page opens.  +
- +
-VCV Complete the following fields for the New Data Sync Run: +
- +
-{{:general:adc_new_data_sync_run.png|New Data Sync Run}} +
- +
-  * In the **District ID** field, click {{:images:dropdown.gif|Drop-down Arrow}} to select the applicable county-district ID. +
-  * In the **School Year** field, click {{:images:dropdown.gif|Drop-down Arrow}} to select the applicable school year (2027). +
-  * In the **School Year Catalog** field, click {{:images:dropdown.gif|Drop-down Arrow}} to select the applicable catalog. +
-  * Under **Domain Selection**: +
-    * Clear the **Select All Domains** checkbox. +
-    * Following the domain dependency order, select one domain at a time. +
- +
-VCV Click **Submit**. +
- +
-2. Review the Level 1 errors and make any necessary corrections in ASCENDER Enterprise. +
- +
-3. As Level 1 Errors become manageable, repeat steps 1 and 2, and continue adding domains in dependency order.  +
- +
-4. After all domains are sending successfully, repeat step 1, except now **Under Domain Selection**, mark the **Select All Domains** checkbox to include all domains in the run. Now, you can begin creating scheduled runs. +
  
 +{{page>academy:adc_createnewrun_body}}
academy/adc_l1errors.1787846769.txt.gz · Last modified: 2026/08/27 16:06 by lcamarillo

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International

Americans with Disabilities Act (ADA) and Web Accessibility

The Texas Computer Cooperative (TCC) is committed to making its websites accessible to all users. It is TCC policy to ensure that new and updated content complies with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. We welcome comments and suggestions to improve the accessibility of our websites. If the format of any material on our website interferes with your ability to access the information, use this form to leave a comment about the accessibility of our website.