matrix table/report

+1! 

Hey Pat,

A component would be great for this! 

But in the mean time you could create something custom.

I found some good looking JS libraries: http://nicolas.kruchten.com/pivottable/examples/ and http://orbjs.net/ which you could easily integrate. Have a look at them and tell me what you think.
If you need help setting that up, just let me know 😉

Cheers

Yep, the pivot table was used before with skuid: https://community.skuid.com/t/pivot-table-like-component

To lazy busy to try to integrate it 😛

I don’t need this that much atm.

I don’t mean to intrude, but would you be able to help me set this up, David? 

+1 A tutorial on this would be awesome

Any update on this idea. We need this kind of report for scheduling. Can anyone help me or guide me to integrate this solution  http://nicolas.kruchten.com/pivottable/examples/ to skuid ?

A workaround using the SFDC Lightning Reports is to use the URL Filtering.

https://help.salesforce.com/articleView?id=reports_filter_url.htm&type=5

Save a report with the filters you want to use. Then go to the report and copy the URL. You only need the part from /Lightning onwards. Then you add the filter number and Skuid merge syntax field. e.g 

/lightning/r/Report/{{sfdc report id}}/view?&fv0={{skuid merge field 1}}&fv1={{skuid merge field 2}}

I use either a table button or a button set and set it to open in new tab.

This won’t work in all use cases and forces users to go away from the Skuid page.

 It would be awesome if Skuid could release a component that can do this within the page. 

There are two ways to get some of those matrix features in Skuid today. 

1. Use decks and context to move data into columns.   This works for things like tasks by day.   
A first model provides all day values (a UI only model,  or an aggregate model on an object guaranteed to have values for all days).  Then a deck on the task model uses context to show data in the right “day” column.   Adjust the card size (and padding) so that all days fit on one line and don’t wrap.  Use a second master model if you want to have a vertical dimension (say owner or category). 

2. Use a template grid.   If your data is static . (like opportunities by quarter) and you can make an aggregate model that guarantees data will always be in the same row - you can use global merge syntax in a template to push data into the appropriate position.  If your model guarantees that row 1 will be Q1, row 2 will be Q2 etc - then use syntax like {{$Model.oppsAgg.data.1.sumAmmount}} to put the Q2 data in the right column. 

Neither of these are as flexible as Nikolas Krutchen’s js plugin,  but we’ve had uneven results trying to get that to work in Skuid.  Ann our examples are currently busted. 

Have fun. 

+1 - this would be a great addition to the skuid arsenal