jamovi

I would like to propose an enhancement to improve data import workflow in jamovi, specifically when copying and pasting data from spreadsheet tools such as Microsoft Excel.

Currently, when users paste data into the Jamovi worksheet, the first row is always treated as data, even if it contains column names. This requires users to manually rename each column header after pasting, which becomes inefficient especially for datasets with many variables.

Use Case (DOE Workflow)
This feature would significantly improve workflows such as Design of Experiments (DOE):

1. A Design Matrix is created in Jamovi
2. The matrix is exported or copied to Excel
3. The response variable(s) are populated in Excel
4. The updated matrix is copied back into Jamovi for ANOVA analysis.

At step 4, the first row typically contains the correct column names (factors and response). Without this feature, users must manually rename all columns again, which is time-consuming and error-prone.

Proposed Enhancement
Introduce a feature in the Data tab that allows users to quickly convert the first row of the worksheet into column headers. For example:
• A button or toggle labeled: “Use First Row as Headers”
• When activated:
o The first row values are assigned as column names
o The first row is removed from the data
o Column types are inferred/refreshed if needed

I believe this enhancement would be practical and beneficial, and I’d welcome your thoughts.

is it easier to simply open the .xlsx file in jamovi? then the column names will come through correctly.

Hi @jonathon,

Thanks for your response.

The problem is that when I open the .xlsx file into Jamovi it opens it in a new session; it doesn't keep the current session that contains the Data Matrix I created during the Create Design phase of my module. Keeping the current session open is important as the module uses the parameters it has produced in the first phase (Create Design) to analyze the output (Design Matrix along with the Response) in the Analyze Phase.

So, your suggestion works with me only if the current session that contains my results retains its output when I open the .xlsx.

Hope this clarifies the use case.

Thanks.

How about "Special Import"?

reason180 wrote: ↑Thu Apr 09, 2026 1:37 am How about "Special Import"?

Thanks. I think "Special import" is sufficient and resolves the problem.