Pronouns are now editable in Identity.UW.
Pronouns are now available in your MyUW profile and in MyUW Class Lists.
During the 2020-2021 academic year, UW will introduce a central pronoun option to enable students and other members of the UW community to express what pronouns they go by in their everyday lives.
Identity.UW will be central to this implementation by enabling the collection and distribution of pronoun data. Person Web Service (PWS) and Student Web Service (SWS) will be providing pronoun data from Identity.UW for campus systems to consume.
Change Details
Although pronoun support in Identity.UW is not available in production yet, we have deployed the capability to support pronoun data in SWS and PWS in both EVAL and Production environments so that you can evaluate integrating pronouns support into your own system(s) if you choose.
Support
For more information on the UW-IT Pronouns implementation and campus-wide rollout, we encourage you to learn more at: https://it.uw.edu/connect/identity/pronouns.
Learn more about integrating pronouns into your own tool(s) via an Enterprise Web Service at https://it.uw.edu/connect/identity/integrate-pronouns-from-identity-uw.
For PWS, please contact us at pws-support@uw.edu
For SWS, please contact us at sws-support@uw.edu
The Capital and Space Management team is migrating to a new Space Inventory Management System.
We are adapting the Space Web Service (SpaceWS) to the source system changes which will result in:
- Some field type and length changes
- Some fields will no longer provide any data (We will NOT remove any fields at this time)
Deployment schedule and opportunity to evaluate:
We have adjusted our schedule in order to coordinate with the updated Space Inventory Management System release schedule. We are now planning to make these changes available in SpaceWS Eval at the end of February 2021 in mid January 2021 and deploy into production March 31 at the end of February.
Change Details:
The list of field changes that may impact you are available on our Wiki at https://wiki.cac.washington.edu/display/EBWS/SpaceWS+v1+Source+Change
Support:
Please contact us at spacews-support@uw.edu if you have any questions or concerns about these changes.
In response to user feedback, the Report Prioritization Group just released enhancements to two BI Portal reports:
This release is timed to help advisers and faculty support Autumn 2020 grading.
Change Summary:
This release is intended to help users identify or filter in/out students who either took a course as an auditor or were granted an RD (registrar drop). We made the following changes:
- Added “RD” to the course grade filter and grade column
- Added “AUD” as a course grade filter and grade column

In the previous report versions, students who audited were not identified in the report’s grade column. Instead, since they didn’t receive a grade, the course grade column displayed blank. To report users, this looked a lot like a missing grade, so we updated the report to display “AUD” instead of blank to distinguish “audit blanks” from “missing grade blanks”.
In Spring 2020, the Office of the University Registrar introduced “Registrar Drop” to replace “HW”, “W” and “W3-W7”. The RD notation began in Spring 2020 for undergraduate, graduate, and professional students. We updated the report so that you can now identify students that receive an RD grade. You can filter on RD in the course grade filter, and view RD in the course grade column. Please note, RD only applies to data beginning Spring 2020. If you filter on RD for older quarters, the report will return no data.
Questions and Feedback:
This report references many UW institutional concepts, including Registrar Drop and Course Grade. To get detailed definitions for these and other terms, please check out Knowledge Navigator!
As always, if you have any questions or if you would like to provide feedback, please write help@uw.edu and put “RPG: Student Grade Reports” in the subject line.
The student database (SDB) will go through a reorganization on January 30, 2021 which will cause changes in the Enterprise Data Warehouse database, UWSDBDataStore. These changes to the objects will be available in the UWSDBDataStore on February 1, 2021.
However, data on the new objects will be available as soon as the Data Custodians submit the security role definitions and the SIS team loads the data.
(last modified: 03.03.2021)
*Please continuously monitor this site for the most current update.
Old Columns to be deleted
Table Name |
Column Name |
registration_courses |
crs_fee_budget |
crs_rev_obj_cd |
crs_cost_acct_cd |
sa_tuition_table |
no_per_std_surch |
sdb_security |
sdb_home_dept |
sdb_org_code |
sr_course_instr |
fac_budget_no |
fac_course_bgt |
fac_wkld_pct |
fac_contact_hr |
fac_is_contact_hr |
sr_instructor |
instr_home_dept |
instr_hepps_fte |
instr_tot_fte |
instr_job_class |
instr_teach_fte |
instr_f_s_hrs |
instr_other_i_hrs |
instr_i_rel_hrs |
instr_admin_hrs |
instr_st_res_hrs |
instr_st_svc_hrs |
instr_sp_res_hrs |
instr_extra1_hrs |
instr_extra2_hrs |
instr_extra3_hrs |
instr_extra4_hrs |
instr_st_res_fte |
instr_st_svc_fte |
instr_sp_res_fte |
instr_extra1_fte |
instr_extra2_fte |
instr_extra3_fte |
instr_extra4_fte |
instr_direct_fte |
instr_i_rel_fte |
instr_admin_fte |
instr_n_s_hrs |
instr_n_s_fte |
instr_st_res_bgt |
instr_st_svc_bgt |
instr_sp_res_bgt |
instr_extra1_bgt |
instr_extra2_bgt |
instr_extra3_bgt |
instr_extra4_bgt |
instr_teaching |
instr_field_2 |
instr_field_3 |
instr_field_4 |
instr_field_5 |
instr_field_6 |
instr_field_7 |
instr_field_8 |
New columns to be added
Table |
Column |
DataType |
dl_origination |
dl_rltn_to_std |
char(1) |
dl_supl_plus |
sp_rltn_to_std |
char(1) |
sa_sf_fund |
fund_wd_tag |
char(12) |
fund_wd_spend_cat |
char(6) |
sa_transaction |
op_dat_crhr1_tag |
char(12) |
op_dat_crhr1_rcat |
char(6) |
sa_tuition_per_cr_hr_charges |
perc_wd_tag |
char(12) |
perc_wd_rev_cat |
char(6) |
sf_evaluation |
ibc_completed_sw |
char(1) |
ibc_completed_dt |
int |
ibc_completed_id |
char(12) |
sr_course_titles |
fee_wd_tag |
char(12) |
fee_wd_rev_cat |
char(6) |
sys_tbl_39_calendar |
frosh_reg_dt_c2 |
datetime |
soph_reg_dt_c2 |
datetime |
junior_reg_dt_c2 |
datetime |
senior_reg_dt_c2 |
datetime |
fifth_yr_reg_dt_c2 |
datetime |
sys_tbl_62_tuit_distrib_subtot |
dtbl_wd_tag |
char(12) |
dtbl_wd_rev_cat |
char(6) |
sys_tbl_63_nontuit_charges |
on_chrg_db_tag |
char(12) |
on_chrg_db_name |
char(12) |
on_chrg_db_rcat |
char(6) |
on_chrg_cr_tag |
char(12) |
on_chrg_cr_name |
char(12) |
on_chrg_cr_rcat |
char(6) |
on_pay_db_tag |
char(12) |
on_pay_db_name |
char(12) |
on_pay_db_rcat |
char(6) |
on_pay_cr_tag |
char(12) |
on_pay_cr_name |
char(12) |
on_pay_cr_rcat |
char(6) |
on_pay_cr_fund |
int |
time_schedule |
fee_wd_tag |
char(12) |
fee_wd_rev_cat |
char(6) |
New Table to be Added
Table |
Column Name |
Datatype |
sa_wd_det_trans |
wd_det_trans_date |
datetime |
wd_det_system_key |
int |
wd_det_seq |
smallint |
wd_det_proc_date |
datetime |
indexd1 |
datetime |
wd_det_proc_pd |
smallint |
wd_det_trans_type |
char(4) |
wd_det_ref_cd |
char(6) |
wd_det_trans_info |
char(20) |
wd_det_company |
char(10) |
wd_det_ledger |
int |
wd_det_tag |
char(12) |
wd_det_spend_cat |
char(6) |
wd_det_rev_cat |
char(6) |
wd_det_db_amount |
decimal(9,2) |
wd_det_cr_amount |
decimal(9,2) |
wd_det_spare_1 |
char(10) |
wd_det_spare_2 |
char(10) |
wd_det_spare_3 |
int |
wd_det_spare_4 |
int |
sa_wd_sum_trans |
wd_sum_trans_date |
datetime |
wd_sum_seq |
int |
wd_sum_proc_date |
datetime |
wd_sum_proc_pd |
smallint |
indexd1 |
datetime |
wd_sum_trans_type |
char(4) |
wd_sum_ref_cd |
char(6) |
wd_sum_trans_info |
char(20) |
wd_sum_company |
char(10) |
wd_sum_ledger |
int |
wd_sum_tag |
char(12) |
wd_sum_spend_cat |
char(6) |
wd_sum_rev_cat |
char(6) |
wd_sum_db_amount |
decimal(9,2) |
wd_det_cr_amount |
decimal(9,2) |
wd_det_spare_1 |
char(10) |
wd_sum_spare_2 |
char(10) |
wd_sum_spare_3 |
int |
wd_sum_spare_4 |
int |
time_schedule_enrl_excl_clas |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_excl_class |
tinyint |
time_schedule_enrl_excl_coll |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_excl_college |
char(1) |
time_schedule_enrl_excl_maj |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_excl_maj_ab |
char(6) |
time_schedule_enrl_excl_sp_p |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_excl_sp_pgm |
tinyint |
time_schedule_enrl_excl_stu |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_excl_stu_grp |
char(5) |
time_schedule_enrl_prioritie |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
enrl_req_honors |
char(1) |
enrl_req_eop |
char(1) |
enrl_req_evening |
bit |
enrl_excl_honors |
char(1) |
enrl_excl_eop |
char(1) |
enrl_excl_evening |
bit |
coreq_course_no |
smallint |
coreq_branch |
char(1) |
coreq_curric_abbr |
char(6) |
coreq_sect_id |
char(3) |
time_schedule_enrl_req_class |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_class |
tinyint |
time_schedule_enrl_req_colle |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_college |
char(1) |
time_schedule_enrl_req_crs_n |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_crs_no |
smallint |
time_schedule_enrl_req_dept |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_dept |
char(6) |
time_schedule_enrl_req_maj_a |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_maj_ab |
char(6) |
time_schedule_enrl_req_sp_pg |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_sp_pgm |
tinyint |
time_schedule_enrl_req_stu_g |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
enrl_req_stu_grp |
char(5) |
time_sched_req_building |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
req_building |
char(4) |
time_sched_req_rm_features |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
req_rm_features |
smallint |
time_sched_req_rm_partition |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
req_rm_partition |
smallint |
time_sched_req_room |
ts_year |
smallint |
ts_quarter |
tinyint |
course_branch |
tinyint |
course_no |
smallint |
dept_abbrev |
char(6) |
section_id |
char(3) |
index1 |
smallint |
index2 |
smallint |
req_room |
char(8) |
Send all questions and concerns to help@uw.edu, with the subject line: “UWSDBDataStore Reorg 01.30.2021“.
On the evening of February 9, 2021, the EDW will be upgrading our user-facing servers (EDWPub.s.uw.edu) to SQL Server 2019. This upgrade will position the EDW to take advantage of modern SQL features, as well as allow for greater flexibility as computing and technology needs evolve.
Impact
We believe this upgrade will have minimal impact on our users. However, we recognize that with any upgrade to a newer version of a relational database management system, there is potential to introduce a compatibility issue with tools or systems that interact with our servers. With this in mind, we have set up an EDW Preview Server for our users to validate before the February 9 production release.
Accessing the EDW Preview Server
The Preview server is available for testing now. We encourage you to test and give us feedback by the end of day January 15, 2021.
Here’s how you can test:
- Direct your query tool or system to EDWPubPreview.s.uw.edu
- Validate that queries run with no error
- If you rely on batch processes, validate that they still run successfully
Known issues
Invalid version error
When connecting to SQL Server 2019, your query tool may return an ‘Invalid version’ error similar to the one below:

You can resolve this error by updating your query tool to the latest version.
The latest version of Microsoft SQL Server Management Studio is available for download here: https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms
ODBC driver not compatible
In order to connect to SQL Server 2019, your ODBC driver needs to be Version 17.3 or higher. The latest ODBC driver for SQL Server is available for download at:
https://docs.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver15
Reporting issues or requesting additional time
We ask that you test at your earliest convenience and acknowledge that you may require additional time. If you experience any issues you are not able to resolve or if you require additional time to validate, please write help@uw.edu and put “EDWPubPreview” in the subject line.
The Report Prioritization Group just released a bug fix on the BI Portal report Undergraduate Transcript Course Search by Major
In this news story we provide a summary of the change. If you have any questions, please don’t hesitate to write help@uw.edu and put “BI Portal Report Question: UG Transcript Course Search by Major” in the subject line.
Change Summary:

Based on user feedback, we resolved an issue in the report logic that was causing students that are registered for a selected course to display as “N” or not registered:
-
For a selected course, show me my majors that are Registered, or have not taken the course:
- This is one of the primary use cases for this report. As an adviser I want to see the following:
- Among my majors
- For a given course (or courses)
- Who has not taken the course and who is currently registered for the course
- Previously the report incorrectly displayed students that are registered for a course as “N” indicating that they have not taken it. This was incorrect and we fixed it.
- The report now correctly displays “Reg” if a student is registered for the chosen course.
Questions?
For more details on the release of this new report, please read this news story in IT Connect: RPG New Report Release: Undergraduate Transcript Course Search by Major
This report references important institutional concepts like “Eligible to Register“, “Student Hold” and many others. If you have questions about the meaning of these or any other terms, please explore the links or find more detail in the Knowledge Navigator.
As always, if you have any questions, please write help@uw.edu and put “BI Portal Report Question: UG Transcript Course Search by Major” in the subject line.
The Data Platform uses ASTRA to manage access to Enterprise Data Warehouse (EDW) data. The recent release of ASTRA 2.1 includes a new auto-deprovisioning feature that will monitor and automatically remove access for terminated employees.
As of December 7, 2020, the EDW is now using ASTRA 2.1 and taking advantage of its new features. The deprovisioning process was previously accomplished via manual review. This automation greatly reduces the risk of inappropriate access to EDW data.
How may this affect you?
- EDW authorizers will benefit from the improved efficiency of automated removal of authorizations. It is still recommended that you continue to review authorizations for terminated employees, job transfers, and others who no longer need access to applications. ASTRA will continue to email quarterly status notifications as reminders.
- EDW users should experience no change in service unless their status changes (e.g. they leave UW). In that case, some user authorizations will be automatically deprovisioned at the time of status change. The EDW Access request process remains unchanged.
A complete overview, including FAQ on the ASTRA 2.1 release, is available at: https://it.uw.edu/security/iam/access/astra/deprovisioning/
Questions or concerns?
If you have questions or concerns, please email us at help@uw.edu with “EDW and ASTRA 2.1 Deprovisioning” in the subject line.
The Report Prioritization Group just released two enhancements to the BI Portal report Major Codes.
This report helps advisers complete the change of major process, and these updates were designed to make it easier to find the info you need to complete the new Docusign web form: Change of Major Forms
This update was requested by a UW adviser and several advisers contributed feedback to the update. Thank you for your help!
Change Summary:
Based on user feedback, we updated the Major Codes filters and columns in the following ways:
Filter Updates
Here’s the filter before:

In the old version of the report, the “Include only Current Codes” filter was causing confusion. We heard things like:
- What is a current code?
- What if a code is active for 2 more quarters? Why is it being excluded?
We updated the filter to allow you to choose from three specific statuses for Major Codes:
- Active
- No longer active
- Not yet active

A Major Code is considered “No longer active” if it has an end date in the past. A Major Code is considered “Not yet active” if it has a start date in the future. All other Major codes are considered Active, whether they have no end date, or whether their end date is in a future quarter.
New Columns
We also updated the column order to improve the usability and added several new columns:

- Major:
- We added a column “Major” with the full Major label as a reference to help you quickly identify the major you’re interested in.
- We moved the Major Name to the 2nd column, also as a quick reference.
- College:
- We added the College name to the College column as a reference.
- Degree Level and Type:
- We added these fields because the form requires it.
- Start and End Quarter:
- We broke these out as separate columns so they’d be more readable.
- Department Name and FAS Org Number:
- We added these fields for departments that need to cross-reference department info in the FAS financial system.
Questions?
This report references important institutional concepts like Change of Major, Student Major and many others. If you have questions about the meaning of these or any other terms, please explore the links or find more detail in the Knowledge Navigator.
As always, if you have any questions, please write help@uw.edu and put “BI Portal Report Question: Major Codes Report” in the subject line.
The Report Prioritization Group just released the newest addition to the BI Portal: Undergraduate Major Comparison by Quarter
In this news story we explain the purpose and benefits of the new visualization. If you have any questions, please don’t hesitate to write help@uw.edu and put “BI Portal Report Question: UG Major Comparisons by Quarter” in the subject line.
It’s All in the Name!
We admit, the visualization has a long name, Undergraduate Major Comparisons by Quarter. But each word explains something about the tool’s function.
- Undergraduate Major: This report allows you to see a population of Undergraduates associated with a major in a given quarter. This dashboard only looks at Undergraduates because an undergraduate can change majors throughout their academic career. They may start as “Pre-Major” then declare a major later, or once they’re “in a major” they may move to another one from quarter to quarter.
- Comparison by Quarter: This visualization allows you to compare a cohort of students across two “reference quarters” like Autumn 2019 and Autumn 2020. The bar on the left shows you the students “in the major” in the first quarter, then shows “where those students were” in the second reference quarter.
How-To:
First, use the quarter filters to choose the two reference quarters that you want to see:

Use the second set of filters to identify the major(s) you want to visualize:

The bar on the left shows you students associated with the major in the “cohort quarter”, the bar on the right shows you the same cohort of students in the future “target” quarter.
You can click a comparison category to filter the detailed table below the bars!

Users and Use Cases:
The primary audience for this report is the academic advising community, and several UW advisers provided significant input on the report’s design! The following are real use cases from our data user community:
The visualization has three primary use cases:
- Advisers in Pre-Major Programs need to:
- Observe if a student leaves a program at a given campus and joins a program at another campus.
- Observe if a student stays at at a given campus, and declares a major. In that case, they want to know the major they joined, and the department that manages it. This helps them to allocate time partnering with those departments so that they can better represent students.
- Departmental Advisers (those who are responsible for students after they ‘declare a major’ e.g. Geography, Computer Science…)
- Observe changes to the population of students they are responsible for. Here, they want to see the ‘flow of students in and out of the major’.
- Advisers can track students in given majors who are not registered for both incoming quarter (Cohort Quarter ) and/or outgoing quarter (Target Quarter)
Questions?
This report references important institutional concepts like Change of Major, Underrepresented Minority Status, and many others. If you have questions about the meaning of these or any other terms, please explore these links or find more detail in the Knowledge Navigator.
As always, if you have any questions, please write help@uw.edu and put “BI Portal Question: UG Major Comparison by Quarter” in the subject line.
In response to user feedback, the Enterprise Reporting and Analytics team just released an update to resolve a bug in the Salary and Wage Expense Detail report in the BI Portal.
Change Summary:
A user reported that the “Year” filter was excluding the current Fiscal Year (2021). By default, the report filters by Calendar Year, but you can filter by Fiscal Year by choosing “Fiscal Year” from the “Period” Filter.
This is what the filter options looked by before the update:

And after the update. You can now select the current Fiscal Year!

Additional Resources:
It can sometimes be confusing to keep all of the different financial years straight, “it’s 2020, and we’re in the 2021 FY, but the 2019 Biennium…”
For a quick reference, we recommend you try the UW Calendars dashboard on the BI Portal! This tool shows you for today, or any date, where the UW is at on the academic calendar, federal fiscal calendar, state biennium calendar, and so on. See for yourself: UW Calendars
Also, we’re updating our report format for a simpler and more modern look and feel. To read more about these changes, check out this news story: 8 Things You Should Know About Our BI Portal Report Format Updates
Questions and Feedback:
This report references many UW institutional concepts, including Account Code and Budget Number. To get detailed definitions for these and other terms, please check out Knowledge Navigator!
As always, if you have any questions or if you would like to provide feedback, please write help@uw.edu and put “BI Portal Question: Salary and Wage Expense Detail” in the subject line.