Based on configuration for this environment, and the collection itself, Edit button should be visible when details page is opened for any record from this Collection for users within specific Role.
I have checked the permissions you have set for your current role and it does not seem to have any issue that would prevent you from editing the “Survey” collection. Do you encounter something similar on other collections or is this a lone case ?
Hi @dogan.ay , now I checked and I’m experiencing this issue in next collections: Surveys, Questions, Users and Results.
In other collections Edit button is visible.
Okey I will need to know now on which fields this error is triggered (Something displaying JSON). Could you show only one JSON at a time and let me know which one triggers the error
@vince
I’m not able to access that feature for collection whit this error. In these collections I do not have a button where i can toggle on/off visibility of specific fields.
Maybe this could help. Since already few months, we noticed that these type of fields contain some additional code from Forest that is not part of our data.
This is an old screenshot we noticed more than 1 month ago