Location tree building issue

In 3.0.0 when building a new location type the checkbox “Selectable as location“ is set to checked (by default) at the time of creation. But set off when I open the type for editing. Enabling again and saving the type does not help. All objects created from the type also have this flag off which retains immutable at any manipulations. No way to build a tree of locations. It remains a flat list. I need your help

Hi @alokhovi ,

thanks for your Feedback regarding this issue. We were not able to reproduce the issue, every type we create keeps the checkbox checked and editing a type also works and keeps the checkbox checked.

Could you provide us a detailed step by step manual so that we can reproduce your issue? If possible give us everything you set/change from the default config in the new type you are creating.

A manual way to fix the issue is changing the value for the checkbox in the database.

Go to the collection “framework.types” and search for the entry of your type (best compare the public_id).

Then change the value of “selectable_as_parent” from false to true. If the value is true in the database but you still do not see the checkbox checked in the frontend, let us know.

Sincerly,

Your DataGerry-Team

Hi Adnan,

took me some time to reproduce the problem too. If you just create a type with the location control you can change the flag and save the type. It works, but when the flag is unchecked and you create an object from this type, it cannot be modified anymore even if all objects created from the type are deleted.

Is it somehow expected? Should I do some special DB cleaning?

Cheers,

Arkady

Hi @alokhovi ,

Thanks for reporting this issue. We were able to reproduce it and have created a Jira ticket DAT-1976. I’ll make sure to update you here as soon as it’s fixed.

Sincerely,

Your DataGerry Team

Hi @alokhovi ,

Thank you for bringing this issue to our attention. We’ve identified and resolved the bug, and the fix is scheduled to be included in the upcoming release.

sincerely,
Your DataGerry Team