Forum Discussion
Unpivoting table Power Query and DAX code
Hi lbendlin Greg_Deckler Anonymous
sorry for delay- Ive been off work ill for 2 weeks.
Can anyone pick up on the 2 issues I encountered on the Power Query, listed in message 27?
ie1. The mystery 'of' and corresponding null value
2. Removing rows (and on an ongoing basis) where there are not resources for a given work itemMany thanks
should be sorted now
You have work items without any resources. How should these be presented? If you want the resources to be unpivoted you have to have data in at least one of them.
hi there lbendlin well- in reality - we will have some work items we log that are potential work that will happen, and so wont hold a resource against them at that point in time, but may allocate a resource at a later date.
How do I need this presented- well, they wont feature in a capacity view, or will have a 'nil' effect, but we would need to be able to allocate resource at a future time and the code to pick up and slot into the capacity report
I would recommend you use separate tables. One for the projects and the other for the assigned resources.
I was just thinking it may be a limiting factor if I understand how you are approaching unpivoting.
So, to confirm, what data are are you suggesting is in each table, and is the creation of the separate tables in Power BI, not at source?
At the moment, all items are held in one SharePoint list in the data source, and preference would be to keep it that way.
Is it possible to split the data in Power BI, creating the two tables?