Those are prebuilt fields/lifecycle roles that come with Portfolios out of the box. If you go into managed attributes you should be able to see the Work Sponsor field.  Chances are you are not using either of those.  When we started using the Portfolios dashboard we had to make several customizations to the backend SQL and Power BI tables to accommodate the custom fields that we created.  You might need to do the same.

Did you create all the datasets in the  > Administration > Reporting > Dataset Management and set up the job streams?

https://success.planview.com/Planview_Portfolios/Analytics_and_Reporting/Power_BI/020_Power_BI_Dashboards/Work_Portfolio_Dashboard/Setting_Up_the_Work_Portfolio_Dashboard

Hi ​@Mario.munoz yes I created all the datasets per the instructions however I don’t see those fields under ‘managed attributes’ and so I’m not able to add them to a configured screen.

Hi ​@Thbutler . thanks for your reply.  I do not see those fields under managed attributes. I think eventually we’ll need to make some changes also but for now I’m just trying to see how to get the out of the box fields populated.  I’m also not getting the traffic lights coming through at the project level assessments. I’ve definitely created the datasets so not sure what I might have missed.

Looks like work_manager and work_sponsor are defined by the customer so they could be another name you can look up by typing the ID (ex..wbs67). We had these but they were under another name. We did have internal Priority. So maybe for the project on the dashboard those attributes were not assigned.

Internal Priority - wbs26

https://success.planview.com/Planview_Portfolios/Administration/Attributes_-_Financial_Planning%2C_Fields%2C_and_Alternate_Structures/070_Alternate_Structures/PDC_4.01.01_en_Planview-Defined_Alternate_Structures

Thanks ​@Mario.munoz . I can see now that this is the case. Huge thanks for pointing me in the right direction. I’m curious as to why the dashboard doesn’t use a lifecycle role for these fields rather than managed attributes. maybe that’s a question for the developer? 

If you look at the sql script (Project_Dimension.sql) you can see it does use the Lifecycle roles. You can edit the script and remove those attributes if not needed or unselect them from Powerbi save it and upload the new copy.