aws-amplify / aws-amplify/amplify-studio

downloading the data on a model containing AWSJson fields incorrectly generates csv rows

Open
#926 1 comment 0 reactions 0 assignees View on GitHub
bug cms studio-ui
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

dqdvhtuddlo4i

### Region

us-east-1

### Environment name

staging

### Figma File Version (if applicable)

_No response_

### Amplify CLI Version

_No response_

### If applicable, what version of Node.js are you using?

_No response_

### What operating system are you using?

_No response_

### Browser type?

_No response_

### Describe the bug

currently the cms has 4 records
image

which generates the id field with text extended from a different row. possibly due to size limitations from https://github.com/aws-amplify/amplify-studio/issues/925
image

### Expected behavior

generate csv in the correct format

### Reproduction steps

1. create a model with for example:
```
type User @model @auth(rules: [{allow: public}]) {
id: ID!
status: AWSJSON
}
```
2. open CMS and select auto generate with 5 records(for example)
3. download to csv and observe the data

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the export in CMS using the shown User model with an AWSJSON field and several generated records. Start by tracing the CMS download-to-CSV path and compare the generated rows with the behavior referenced in issue 925. Done means each record produces a correctly separated CSV row without text from another record.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.