This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
Hi,
I'm using the following API to pull json data into Power BI:
https://www.aha.io/api/resources/custom_pivot
I'm using the list view.
The json data comes in in Pagination, Columns and Rows.
Expanding coumns, I get 28 rows of data. These are the column headers in my list.
Expanding rows, I get >1000 lines. Each repeating 28 rows of data, should be one row in the table (corresponding with the 28 column headers above).
I'm wondering if anyone has any hints on how to combine the 2 data sources into one table?
For example
| Table: columns | |
| Column1.title | |
| 1 | Product Line (Product line) |
| 2 | Product name |
| 3 | Product ID |
| 4 | Release name |
| 5 | Release ID |
| 6 | Release created at |
| 7 | Release start date |
| 8 | Release date |
| 9 | Release owner |
| 10 | Release status |
| 11 | Feature name |
| 12 | Feature ID |
| 13 | Feature created at |
| 14 | Feature start date |
| 15 | Feature due date |
| 16 | Feature status |
| 17 | Feature URL |
| 18 | Requirement assigned to |
| 19 | Jira id |
| 20 | JIRA Sprint |
| 21 | Jira key |
| 22 | Jira url |
| 23 | Requirement name |
| 24 | Requirement ID |
| 25 | Requirement created at |
| 26 | Jira id |
| 27 | Jira key |
| 28 | Jira url |
| Table: rows | |
| Column1.plain_value | |
| 1 | Product Line (Product line) 1 |
| 2 | Product name 1 |
| 3 | Product ID 1 |
| 4 | Release name 1 |
| 5 | Release ID 1 |
| 6 | Release created at 1 |
| 7 | Release start date 1 |
| 8 | Release date 1 |
| 9 | Release owner 1 |
| 10 | Release status 1 |
| 11 | Feature name 1 |
| 12 | Feature ID 1 |
| 13 | Feature created at 1 |
| 14 | Feature start date 1 |
| 15 | Feature due date 1 |
| 16 | Feature status 1 |
| 17 | Feature URL 1 |
| 18 | Requirement assigned to 1 |
| 19 | Jira id 1 |
| 20 | JIRA Sprint 1 |
| 21 | Jira key 1 |
| 22 | Jira url 1 |
| 23 | Requirement name 1 |
| 24 | Requirement ID 1 |
| 25 | Requirement created at 1 |
| 26 | Jira id 1 |
| 27 | Jira key 1 |
| 28 | Jira url 1 |
| 1 | Product Line (Product line) 2 |
| 2 | Product name 2 |
| 3 | Product ID 2 |
| 4 | Release name 2 |
| 5 | Release ID 2 |
| 6 | Release created at 2 |
| 7 | Release start date 2 |
| 8 | Release date 2 |
| 9 | Release owner 2 |
| 10 | Release status 2 |
| 11 | Feature name 2 |
| 12 | Feature ID 2 |
| 13 | Feature created at 2 |
| 14 | Feature start date 2 |
| 15 | Feature due date 2 |
| 16 | Feature status 2 |
| 17 | Feature URL 1 |
| 18 | Requirement assigned to 2 |
| 19 | Jira id 2 |
| 20 | JIRA Sprint 2 |
| 21 | Jira key 2 |
| 22 | Jira url 2 |
| 23 | Requirement name 2 |
| 24 | Requirement ID 2 |
| 25 | Requirement created at 2 |
| 26 | Jira id 2 |
| 27 | Jira key 2 |
| 28 | Jira url 2 |
| 29 | etc etc (Repeats in 28 row blocks) |
Desired output:
| Product Line (Product line) | Product name | Product ID | Release name | Release ID | Release created at | Release start date | Release date | Release owner | Release status | etc |
| Product Line (Product line) 1 | Product name 1 | Product ID 1 | Release name 1 | Release ID 1 | Release created at 1 | Release start date 1 | Release date 1 | Release owner 1 | Release status 1 | etc |
| Product Line (Product line) 2 | Product name 2 | Product ID 2 | Release name 2 | Release ID 2 | Release created at 2 | Release start date 2 | Release date 2 | Release owner 2 | Release status 2 | etc |
Thanks in advance for the help!
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |