Skip to main content

Community

Connector Improvement: Add new fields to workramp connector - path_assignment table

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Sachin Vyas,

    Thank you for taking the time to share your feature request regarding the addition of fields to the WorkRamp path_assignment table. We greatly appreciate your input and are always looking for ways to enhance our platform to better meet the needs of our users.

    I am pleased to inform you that we have added your request to our backlog. We will prioritize this feature based on demand and other strategic factors. Rest assured, we are committed to keeping our community informed, and we will share any updates regarding the progress of this request as they become available.

    Thank you once again for your valuable contribution.

    Best regards,  
    Syead Mujtaba Imam Rizwi

    Thanks Syead,

    adding the concise request as we need few more features for guide_assignment as well.

    WorkRamp Connector: Missing columns in path_assignment and guide_assignment

    Hi team,

    We've identified fields returned by the WorkRamp API that are not currently synced into two tables in Snowflake.


    1. path_assignment

    API endpoint: GET /paths/{path_id}/assignments https://developers.workramp.com/reference/get-all-assignments-for-a-path

    Missing columns:

    Field Type
    status string (not_started, in_progress, completed)
    is_completed_on_time boolean
    passed boolean
    passing_grade_required boolean
    is_overdue boolean
    num_days_overdue integer
    first_accessed_at timestamp
    last_accessed_at timestamp

    2. guide_assignment

    API endpoint: GET /assignments/guide https://developers.workramp.com/reference/get-all-guide-assignments-in-date-range

    Missing columns:

    Field Type
    is_completed_and_passed boolean
    is_deleted boolean
    is_mandatory boolean
    last_viewed_at timestamp

    All fields above are confirmed present in the respective API responses but absent from the destination tables.

    Could you please add these columns to both table schemas? Also happy to know if a historical re-sync will be needed to backfill, or if they'll populate going forward only.

    Thanks!