Relationships to deleted relations and attributes not cleared.

francis_mat

Hi,

Me being new to REI3 had to experiment a lot, as a lot of questions in hte communty forum etc. to make things work.

I had created different relations, different attributes to these relations and also different relationships.
Later on, I deleted many of these.

Now I'm facing issues of relationships with non-existing relations, attributes and forms.

For example, I have a frn_payments relation table, which had many attributes. I no longer need this relation, but constraints were not allowing me to delete this relation. So i tried to delete attributes, and ended up with one foreign key to frn_bookings relation.

Hi,

Me being new to REI3 had to experiment a lot, as a lot of questions in hte communty forum etc. to make things work.

I had created different relations, different attributes to these relations and also different relationships.
Later on, I deleted many of these.

Now I'm facing issues of relationships with non-existing relations, attributes and forms.

in the below shown relationship graph of frm_payments it shows relation to no existing relation table of frm_guests, which I have deleted earlier.

Also, other relationship attributes like frm_bookingd.payrefundamount_id , frm_bookingd.paybookingadvancepayment_id etc do not exist anymore on frn_bookings relation.

Other relationsship attributes except booking_id do not exist on frn_payments.

How do I clean this mess I created? Or do i need to re-create the entire application?

Cheers
Francis

gabriel

Hello Francis,

Sometimes, when you have many interconnected relations, it can be complicated to resolve, where what is used. The easiest path would be, to delete the relationship attributes on these relations first. Everytime you try to delete an attribute, REI3 will either just do it, or show you, where its still being referenced.

You definitely do not have to redo your application. It´s just a question of untangling your relations. There are also no ghost (e.g. previously deleted relations) hanging around - if you cannot delete something, there is still a valid reference to it. Going through the attributes is a good way to clean it up quickly.

francis_mat

After restarting the browser except one relation everything is gone.

Looking like it was cached somewhere?

Now frn_payments.booking_id is supposedly being used in booking_edit page. I'm trying to figure out where?

Cheers
Francis

gabriel

Browser caching issues are possible - which version are you running, R3.7.1?

The reference from your screenshot, points to a list field on the form frn_hospitality_management. Attributes in list fields can be referenced as columns, in filters, for joins and in sub queries. When you click on the link list from the screenshot, the referencing list field is marked.

francis_mat

gabriel
Platform version 3.7.0.5110
Do I need to update now?

I should have tried the link, but my mind was already too tired. I deleted whole contents of the page, now cleared the data design around that area.

Also, I found that if a reference of a field is in commented out code in functions exists, I cannot delete that field.

Cheers
Francis

gabriel

Updating patch releases (like 3.7.2) is always recommended, because they mostly address bugs. There were a couple of caching issues in 3.7, if I remember correctly. Updating to a new minor version (3.8 would be the next one) is also usually a good idea though there is a higher chance of bugs because new features are being introduced.

francis_mat Also, I found that if a reference of a field is in commented out code in functions exists, I cannot delete that field

Yes, our parser (that checks for references) is not smart enough currently to safely ignore comments. It´s a limitation to be sure.

francis_mat

gabriel
Thanks Gabriel.
I'll update to 3.7.2 for the time being..

Yes, our parser (that checks for references) is not smart enough currently to safely ignore comments. It´s a limitation to be sure.

Not a major issue. Just brought it to your notice that's all. Once I know the parser works like that I know where all to look. Good idea to add this information in docs.

Cheers
Francis

gabriel

From my experience, most skip our docs. It might be a better idea to add the info to the UI directly or fix the issue outright - it´s usually best, if documentation is not required at all 🙂