# Regression issue

**URL:** <https://community.forestadmin.com/t/regression-issue/916>\
**Category:** Help me!\
**Created:** [September 6, 2020, 1:22pm UTC](https://community.forestadmin.com/t/regression-issue/916 "2020-09-06T13:22:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Louis-Marie](https://avatars.discourse-cdn.com/v4/letter/l/258eb7/32.png) [@Louis-Marie](https://community.forestadmin.com/u/Louis-Marie)\
**Post date:** [September 6, 2020, 1:22pm UTC](https://community.forestadmin.com/t/regression-issue/916/1 "2020-09-06T13:22:48Z")

</div>

Hi,

Following the last update on this issue [Performance issue](https://community.forestadmin.com/t/performance-issue/188) I have just tried the last release of forest-express-sequelize which is 6.3.9.

I have now a new issue: when a “reference” column of an associated relationship is defined to use a “smart field” (instead of a native field), the parent list is generating an error.

_Examples_:  
_With the same collections as previously (“`users`” and “`crm_user_exchanges`”), if the `crm_user_exchanges` collections is defined to use a smartField named “`crm_ref`” then displaying the associated collection in `users` collection will generate a sequelize error:_

> column crm\_user\_exchanges-\>regarding.crm\_ref does not exist  
> DatabaseError [SequelizeDatabaseError]: column crm\_user\_exchanges regarding.crm\_ref does not exist

I have now the same issue with hasOne relationShips.  
_Let’s take this one:_

> db.users.hasOne(db.kyc);

_Displaying the list of users is generating an error:_

> [forest] 🌳🌳🌳 Unexpected error: column kyc.Onboarding does not exist  
> SequelizeDatabaseError: column kyc.Onboarding does not exist

_Because the “`Onboarding`” field used a reference for the “`kyc`” collection is a smartField, not a native field._  
_If I replace the smartField by a native field in the “reference” of the “`kyc`” collection, the error disappears._

- “database\_type”: “postgres”,
- “liana”: “forest-express-sequelize”,
- “liana\_version”: “6.3.9”,
- “engine”: “nodejs”,
- “engine\_version”: “12.13.1”,
- “framework”: “express”,
- “framework\_version”: “^4.17.1”,
- “orm\_version”: “4.44.0”

Thanks in advance for your help

---

<div class="post-metadata">

**Author:** ![arnaud](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud/32/32_2.png) [@arnaud](https://community.forestadmin.com/u/arnaud)\
**Post date:** [September 7, 2020, 7:02am UTC](https://community.forestadmin.com/t/regression-issue/916/2 "2020-09-07T07:02:31Z")

</div>

Hi @Louis-Marie,

Thanks for your feedback,  
Could you share with use the implementation of your Smart Field and precise what native fields are necessary to compute this Smart Field? It would help a lot to reproduce and fix the issue.

Thank you.

---

<div class="post-metadata">

**Author:** ![arnaud](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud/32/32_2.png) [@arnaud](https://community.forestadmin.com/u/arnaud)\
**Post date:** [September 7, 2020, 10:31am UTC](https://community.forestadmin.com/t/regression-issue/916/3 "2020-09-07T10:31:31Z")

</div>

Here is another post related to this topic:

> [@Latest forest-express-sequelize breaks smart fields](https://community.forestadmin.com/t/latest-forest-express-sequelize-breaks-smart-fields/897/10):
>
> Hi @austinrupie, @Cyril_Limam, We reproduced the issue thanks to your latest messages pray. The team is currently working on a fix. If you need a safe spot, you should definitively downgrade your forest-express-sequelize package version to 6.3.6. We’ll let you know once a new patch version is available. Thanks for your patience.

---

<div class="post-metadata">

**Author:** ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)\
**Post date:** [September 8, 2020, 12:20pm UTC](https://community.forestadmin.com/t/regression-issue/916/4 "2020-09-08T12:20:21Z")

</div>

@Louis-Marie we released the version `6.3.10` which contains the fix for your issue.

Can you try it on your project?

---

<div class="post-metadata">

**Author:** ![Louis-Marie](https://avatars.discourse-cdn.com/v4/letter/l/258eb7/32.png) [@Louis-Marie](https://community.forestadmin.com/u/Louis-Marie)\
**Post date:** [September 13, 2020, 2:44pm UTC](https://community.forestadmin.com/t/regression-issue/916/6 "2020-09-13T14:44:38Z")

</div>

Hi @GuillaumeGautreau,

I do not have the “Reference” problem any more.

I think the regression issue is fixed.  
I still have the performance issue, but will continue on that other post.

Thanks.