如何在Rails中使用ReportKit创建多列表格报表？求解决方案

Let's work through getting your multi-column table up and running. From looking at your code, the main issues are mismatched configurations between your model's ReportKit setup and the YAML report definition, plus some small syntax/naming inconsistencies.

Step 1: Correct Your Model's ReportKit Configuration #

First, let's clean up your model code to ensure table names, associations, and definitions align with Rails conventions and ReportKit's expectations:

reports_kit do
  # Fix aggregation: Use proper table names (plural) and format the time difference
  aggregation :average_time_to_publish, 
              [:average, 'EXTRACT(EPOCH FROM (sales.created_at - posts.updated_at))'], 
              label: "Avg. Publish Time (Seconds)"
  
  contextual_filter :for_author, ->(relation, context_params) { 
    relation.where(sale_id: context_params[:sale_id]) 
  }

  # Fix dimension table name (sales, not sale) and add a clear label
  dimension :approximate_views_count, 
            group: 'ROUND(sales.views_count, -1)', 
            label: "Approximate Views"
  
  filter :is_published, :boolean, conditions: ->(relation) { 
    relation.where(status: 'published') 
  }

  # Add explicit dimensions for the columns you want in your table
  dimension :sale_id, label: "SALE ID"
  dimension :created_at, label: "Created At", format: "%Y-%m-%d %H:%M"
end

Key fixes here:

• Pluralized table names (sales instead of sale) to match Rails default conventions
• Formatted the time difference aggregation using EXTRACT(EPOCH FROM ...) to get a numeric average (easier to display)
• Added explicit dimensions for the columns you want to include in your table

Step 2: Update Your YAML Report Definition #

Your YAML was missing proper measures configuration (you used a single measure instead of an array) and didn't map correctly to your model's dimensions. Here's the revised version:

# Use measures array to define multiple metric columns
measures:
  - key: average_time_to_publish
    label: Avg. Publish Time
  - key: cashier_name
    label: Cashier Name

filters:
  - key: sale_id
  - key: created_at
    criteria:
      operator: between
      value: "-3M - now"

# Define all dimensions you want as columns in your table
dimensions:
  - key: sale_id
    label: SALE ID
  - key: created_at
    label: CREATED AT
  - key: approximate_views_count
    label: Approximate Views

format: table

# Optional: Add sorting to organize your table
sort:
  - key: created_at
    direction: desc

Why this works:

• The measures array lets you include multiple numeric/aggregated columns in your table
• Each entry in the dimensions array becomes a dedicated column in the table
• All keys directly map to the dimensions/aggregations you defined in your model

Step 3: Verify the Output #

After making these changes, your table should render with:

• 3 dimension columns (SALE ID, CREATED AT, Approximate Views)
• 2 measure columns (Avg. Publish Time, Cashier Name)
• Applied filters for sale_id and date range

If you're still seeing issues, double-check:

1. That your model associations (like Sale ↔ Post) are properly defined
2. That all column names in your aggregation/dimension definitions exist in your database tables
3. That you're passing the correct context_params if using the for_author contextual filter

内容的提问来源于stack exchange，提问作者Wunna Tun