US English (US)
ES Spanish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Log in
English (US)
US English (US)
ES Spanish
  • Home
  • Help & Support
  • Support
  • Support FAQs
  • FAQ: Integration

SDOC Version 9.0 Upgrade – Update Required for Generated Document Visibility

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • RIO Certification
    RIO Certification Program RIO Academy RIO Challenge RIO Recipe Training
  • Releases
    V3 Release Notes V4 Release Notes
  • Help & Support
    Install RIO Education RIO Insights RIO Recipe Support RIO Graduate/Intern Program Trainee (GPT)
  • Experience RIO in action
  • RIO Insights
+ More

Table of Contents

Overview Impact Resolution

Overview

 

This article explains the SDOC upgrade change where the generated file's Content Version Id is now stored in SDOC__File_Version_ID__c instead of SDOC__File_ID__c. Any custom code, automation, or logic that references the legacy field must be updated to use the new field to ensure generated documents continue to be processed and displayed correctly.

 

A new field has been introduced in the SDOC__SDoc__c object in the latest SDOC version:

 

  • New Field: SDOC__File_Version_ID__c
  • Previous Field: SDOC__File_ID__c (Still exist in version 9.0) 

In previous SDOC versions, when a PDF document was generated (such as an Official Transcript, Unofficial Transcript, or Degree Audit), the generated file's Content Version Id was stored in the field: SDOC__File_ID__c

With the newer SDOC version, the generated file's Content Version Id is now stored in: SDOC__File_Version_ID__c

As a result, the original field SDOC__File_ID__c is no longer populated with the Content Version Id for newly generated documents.
 

Impact

The Community Portal uses a custom trigger named: redu_SDoc_Visibility_TDTM

This trigger retrieves and displays student-generated documents by using the field SDOC__File_ID__c as a key value.

Since the newer SDOC version now stores the Content Version Id in SDOC__File_Version_ID__c instead, the value in SDOC__File_ID__c becomes null for newly generated documents.

This causes:

  1. The trigger's key field lookup to fail.
  2. The generated map to be empty.
  3. Student-generated documents not to appear in the Community Portal.

Resolution

Update all references of by replacing SDOC__File_ID__c with SDOC__File_Version_ID__c within the custom class.

Component to update:

  1. Apex Class
    • redu_SDoc_Visibility_TDTM
  2. Associated Test Class
    • Update all test data and assertions that reference SDOC__File_ID__c.

Validate after applying the changes:

  1. Generate a document (Official Transcript, Unofficial Transcript, or Degree Audit).
  2. Confirm that the generated SDOC__SDoc__c record contains a value in SDOC__File_Version_ID__c.
  3. Verify that the document is successfully displayed in the Community Portal.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • USI Integration Update: Transition to TLS 1.3
  • Cannot select multiple courses to be queued for Canvas Grade Sync
RIO Education

RIO Education, a WDCi Company. This information is proprietary, confidential and protected by copyright ©2024.

CONTACT

Get in touch

  • Privacy
  • Terms of service

Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
Expand