# SHACL messed up in studio

**URL:** <https://community.stardog.com/t/shacl-messed-up-in-studio/3446>\
**Category:** Bug\
**Created:** [January 10, 2022, 2:09pm UTC](https://community.stardog.com/t/shacl-messed-up-in-studio/3446 "2022-01-10T14:09:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zorgoz](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/zorgoz/32/1166_2.png) [@zorgoz](https://community.stardog.com/u/zorgoz)\
**Post date:** [January 10, 2022, 2:09pm UTC](https://community.stardog.com/t/shacl-messed-up-in-studio/3446/1 "2022-01-10T14:09:08Z")

</div>

It looks to be some confusion between the "Constraints" and "Text editor" tab but also with the constraint rendering.

1. The constraints written and saved in SHACL in the "Constraints" are rendered in the "Text editor" but with the wrong syntax, making changes impossible until they are manually corrected.  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/5/5289ddf9b6a41c4dcf9da12ecf59de368686d5f4.png)  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/d/dce35bd9798c54fb471ee5ffdd3a2e8a4ac307dd.png)
2. If corrected here, they reappear in the "Constraints" tab with wrong syntax  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/f/fe2b464635de4434c19e5538a1c2ba0fdbbf38b8.png)  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/a/a91ce590f22ddfcd314e77afc386e4b18857eb7e.png)

Is there any solution or workaround?

---

<div class="post-metadata">

**Author:** ![pavel](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/pavel/32/18_2.png) [@pavel](https://community.stardog.com/u/pavel)\
**Post date:** [January 11, 2022, 6:05pm UTC](https://community.stardog.com/t/shacl-messed-up-in-studio/3446/2 "2022-01-11T18:05:13Z")

</div>

Hi Zoltán,

Indeed it looks like Studio does a bit of higher-level parsing for SHACL than just RDF and doesn't expect stuff like object lists in there. We created an internal ticket VET-1438 and will look into it. We'll let you know if there're workaround (other than editing and loading via CLI, of course, which is always a possibility).

Thanks for the report,  
Pavel