# Creating and Deleting records is not very intuitive

**URL:** <https://community.forestadmin.com/t/creating-and-deleting-records-is-not-very-intuitive/728>\
**Category:** Feature suggestions\
**Tags:** howtos\
**Created:** [July 26, 2020, 11:02pm UTC](https://community.forestadmin.com/t/creating-and-deleting-records-is-not-very-intuitive/728 "2020-07-26T23:02:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![BK42](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bk42/32/568_2.png) [@BK42](https://community.forestadmin.com/u/BK42)\
**Post date:** [July 26, 2020, 11:02pm UTC](https://community.forestadmin.com/t/creating-and-deleting-records-is-not-very-intuitive/728/1 "2020-07-26T23:02:32Z")

</div>

## What is the feature?

For the folks who have not used this tool before, it is very error-prone and confusing to create and delete records using the current interface. See this detailed walkthrough to see what I mean where I discuss three specific points: [https://www.loom.com/share/1965d88586e54f32b27ae1544ad9ff3a](https://www.loom.com/share/1965d88586e54f32b27ae1544ad9ff3a)

## What problem does this solve for you?

Makes forest admin easy to use for non-technical folks or even technical folks who have are not used to some of the quirks.

## Who else would be using this feature?

Both technical and non-technical folks.

---

<div class="post-metadata">

**Author:** ![anon20071947](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@anon20071947](https://community.forestadmin.com/u/anon20071947)\
**Post date:** [August 13, 2020, 5:50pm UTC](https://community.forestadmin.com/t/creating-and-deleting-records-is-not-very-intuitive/728/2 "2020-08-13T17:50:41Z")

</div>

Hello again @BK42 😃

Thanks for your elaborate feedback, let me provide some hints & tips for you here.

**1. Regarding the auto-complete feature based on existing values**  
This is _possible_ if you know in advance that your field is bound to certain values. In your field’s EDIT SETTINGS, set a `dropdown widget` with the content values and enable search.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/6b4f1188f7f9ff5b1abb2df9959608e7fdb139fa.png)

**2. Creating (or associating an existing) related record in collection B from collection A’s view**  
You’re right about this! I just realized that when there are no associated records, `Create the first one` button does not give you the choice between creating a new related data record or associating an existing one.  
For this, I suggest you click on the green `+` button in top-right corner. You’ll get the 2 options.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/27942390737bd17c5c12ad96660c95eb7e815844.png)

I’ll make sure an insight is logged in our Productboard for a second `Add an existing one` button

**3. Related record not showing up after its creation**  
This is pretty straightforward, you’re trying to create a child record when the parent record hasn’t been created (persisted to database) yet.  
Bottomline is you can’t associate something recently created…to something that doesn’t exist yet 😅 Simply start by saving the parent record first.

**4. ForeignKey constraint violation upon parent/child record deletion**  
Forest Admin (through the sequelize ORM) cannot do what the database does not allow you to. It merely follows its rules. I suggest you take a look at what the PostgreSQL and Sequelize docs have to say about this. Tweaking your database and models should allow you to achieve the desired outcome.

- [https://www.postgresql.org/docs/12/ddl-constraints.html#DDL-CONSTRAINTS-FK](https://www.postgresql.org/docs/12/ddl-constraints.html#DDL-CONSTRAINTS-FK)
- [https://sequelize.org/master/manual/assocs.html#-code-ondelete--code--and--code-onupdate--code-](https://sequelize.org/master/manual/assocs.html#-code-ondelete--code--and--code-onupdate--code-)

Let me know if this helps!