Skip to main content
Question

Reporting Logbook data with Power BI-Error

  • February 3, 2026
  • 1 reply
  • 40 views
S
Bronze Innovator
Forum|alt.badge.img+2

We are using Logbook’s “Other” category to log data (name, date, team, comments) on our projects. We would like to be able to have a view showing ALL comments in one place...rather than having to go to each project and open the Logbook tab to see if there are any comments.  

I am using the Logbook Template V1.2.pbit to try and create a view showing all Work items that have a Logbook entry associated with them.   In Power BI I’m trying to create a Matrix where the Rows are the Work item data and Logbook entry “name” (EntityAssociations: EntityID & EntityAssociations:EntityName, LogbookItems: Name), the Columns are the CustomAttributesConfigs: Name and the Values are the CustomAttributes: Value.value

When I try to use the CustomAttributeConfigs fields with the EntityAssociations fields in the same visual, I get an error - “Can’t determine relationships between the fields”.  I get this error when I try to use these in the same visual.  I can put them in separate visuals (list projects in one box with the name of the logbook item. Click on the logbook item name and show the detail information in a box below), but it doesn’t create the view I would like to see.  

Has anyone done anything similar and had success?  We are currently only in the sandbox, but hope to release Logbook use in the next month.  

Thank you in advance.

Sonia

    1 reply

    mserafinowski
    Bronze Product Expert
    Forum|alt.badge.img+2
    • mserafinowski
    • Bronze Product Expert
    • February 5, 2026

    Hi ​@SVarney 

    I’m not entirely sure what you’re trying to achieve but I can explain how we tackled this in our logbook dashboard. We have separate pages for each Log Type, for example: risks, issues, dependencies. I assume yours would fall under “Other”. If that’s the case, here’s how I would structure it:


    Create a table containing:

    LogItems[LogId]
    Work_ID, Work_Name
    LogItems[Name], LogItems[Description]
    CustomAttribute[xxx]     (your comment field)

    On the Page filter use LogTypeCategories[Name] and select the category you need, in your case likely “Other”.


    You can then add slicers for Projects or Portfolio, Portfolio, depending on your dataset and where you’re going to consume the dashboard. To enable this, we added the Project_Dimension and PortfolioDashboards_Project_Portfolio_Dimension tables to the model and created the following relationship:
    LogContainers[ContainerId] → Project_Dimension[ppl_code]
    (Many-to-One)

    Another recommendation is to unpack the Custom Attribute table. Instead of having custom attributes as rows, pivot them into separate columns. It’s similar to unpivoting in reverse. For us, this made a big difference, otherwise we couldn’t use multiple custom attributes in a single visual.

    I’m not saying this is the perfect or best practice solution but it enabled many things in our logbook dashboard and we also consume the logbook data in many other reports.

    Give this approach a try, it may help you build the overview you’re trying to achieve. 

    Best, 
    Michal 

    Terms of UseCookie settingsAccessibility statement
    All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

    Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com