Introduction

We were experiencing slow query times in the Reimpact platform when using Eloquent subqueries with anonymous models. The issue stemmed from unintended default ordering and a mismatch between the model table and the subquery alias.

The Problem

Eloquent was automatically adding an ORDER BY pulse_entries.id clause, even though `pulse_entries.

The Reimpact/platform project is focused on [description]. Recent development efforts have concentrated on improving the way DPR (Data Protection Report) data is presented and managed within the platform. This involved transitioning from a static HTML table to a dynamic Filament TableWidget, offering enhanced features such as pagination, search, filtering, and translation support.

Introduction

The Reimpact/platform project focuses on providing a streamlined user experience. Recent efforts have been directed towards improving the layout and responsiveness of sections within the platform.

The Challenge

Previously, sections on the platform did not always stack vertically as intended on smaller screens or when content required full width.

Working with large datasets in Filament can sometimes be overwhelming. Displaying all the information at once can make it difficult to quickly grasp key insights. This post explores how to enhance Filament tables by collapsing details by default and using translated filters for a more user-friendly experience, as recently implemented in the Reimpact/platform project.

Collapsing Details by

Introduction

When working with Filament, especially when displaying data from sources other than Eloquent models, you might encounter situations where the built-in features for filtering, searching, sorting, and pagination don't work out of the box. This post describes how to manually implement these features for array-based report tables within Filament admin panels.

The Challenge: Array

The Reimpact/platform project is undergoing improvements to its data presentation layer, focusing on enhanced readability and structural clarity. This involves reformatting data reports to be more user-friendly and logically organized.

Enhanced Data Reporting

The recent work centers around improving the way data reports are rendered. Instead of repeating headers for each row in a data

Introduction

When working with database migrations and seeders in Laravel, particularly with PostgreSQL, developers sometimes encounter issues related to SQL parsing. One such issue arises when attempting to seed data into a table that already exists but is missing a specific column.

This post discusses recent enhancements to the report generation process within the Reimpact/platform project, focusing on storing and displaying the generated report data.

The Feature

The primary goal of these changes is to persist generated report data and provide flexible views for different report types. This involves adding a report_data column to the packaging_generated_reports

Introduction

The Reimpact platform is undergoing continuous improvements to enhance its data model and overall efficiency. One recent focus has been on refining relationships between models to ensure data integrity and reduce redundancy.

The Challenge

In a recent update, a specific issue was identified within the LatestMassiveUploadsWidget. The MassiveUpload model, designed for

Introduction

When performing database migrations, especially in multi-tenant environments, it's crucial to ensure all aspects of the schema are correctly applied to each tenant. This post explores a scenario in a Laravel application where PostgreSQL functions were unintentionally dropped during a tenant migration and how they were recovered.

The Problem: Silently Missing Functions