Skip to content

Shaun Walker

My feedback

4 results found

  1. 149 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 77 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Aeries Ideas  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Shaun Walker supported this idea  · 
  4. 142 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Unfortunately, we are unable to move forward with this request until CALPADS makes changes in its system to allow SIS Vendors to access the API like the Special Ed Vendors can. While this enhancement is not currently on our roadmap, we appreciate your feedback and will keep it in mind for future consideration.

    An error occurred while saving the comment
    Shaun Walker commented  · 

    I would like to have the option to still extract the file just in case CALPADS continues to have the current redesign issues and we have a work around. Also, I agree with Ryan Bahten... Would like to make sure that we, as the end user at the School/District level, still have control over when and what data is exchanged via this API. Just want to make sure it's configurable so that we are the ones "pushing the button" so that we know when and what data is being shared and transferred between Aeries and CALPADS.