aws-amplify / aws-amplify/amplify-studio

model with two index fields generates cms form that does not allow modifying the join

Open
#896 0 comments 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

d3ovbf1bxv8221

### Region

us-east-1

### Environment name

dev

### 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

When using CMS form with that connects a model with two index fields, the connection cannot be modified.

https://user-images.githubusercontent.com/87995712/229879683-a7c20b18-844f-4bfa-b8e1-84ec3c751aa3.mov

### Expected behavior

allow modifying a join on the form

### Reproduction steps

1. create a model such as follows
```graphql
type Comments @model @auth(rules: [{allow: public}]) {
id: ID!
comment: String
testID: ID! @index(name: "byTest")
userID: ID! @index(name: "byUser")
}

```
2. deploy and open cms
3. create a record as shown in the video and observe the error in browser console.

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start in the CMS form entry point and reproduce the model with two indexed fields from the issue, then inspect the browser console during join editing. Done means the generated form allows the connection to be modified without the reported console error.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql
Domain
backend-api-design, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.