Field deactivation/deletion issue
Hi!
I posted this problem few days ago:
💻︱development
In short:
"We decided to change in workspace type of few fields to make them clickable.
From text to link.
As I understand to change type you have to delete old field and create new one.
Steps to Reproduce:
First I deactivated 5 columns. Then I clicked them fast to delete.
Expected Behavior:
5 fields deleted.
Actual Behavior:
Not all fields deleted. Business process broke."
Got error "column lead.fb does not exist".
And error "column fb was not found in "workspace_name._lead".
I tried to change tables in postgres, but eventually could not solve problem.
Today two things happen:
1) I found post with bug which by description is what I faced. Except in example were deleted fields with type relation and I deleted type text.
Here it is: https://www.answeroverflow.com/m/1379398545756393663
And it is stated that it was fixed about 2 weeks ago.
I could not figure if 0.55.6 version contained that fix.
2) I moved to new 1.0.0 twenty build and reset postgres db.
Now I will recreate all the fields and relations.
So I worried If the problem with field deletion is fixed in the latest builds (1.0.0/1.0.2) or I can face it again any moment?
I posted this problem few days ago:
💻︱development
In short:
"We decided to change in workspace type of few fields to make them clickable.
From text to link.
As I understand to change type you have to delete old field and create new one.
Steps to Reproduce:
First I deactivated 5 columns. Then I clicked them fast to delete.
Expected Behavior:
5 fields deleted.
Actual Behavior:
Not all fields deleted. Business process broke."
Got error "column lead.fb does not exist".
And error "column fb was not found in "workspace_name._lead".
I tried to change tables in postgres, but eventually could not solve problem.
Today two things happen:
1) I found post with bug which by description is what I faced. Except in example were deleted fields with type relation and I deleted type text.
Here it is: https://www.answeroverflow.com/m/1379398545756393663
And it is stated that it was fixed about 2 weeks ago.
I could not figure if 0.55.6 version contained that fix.
2) I moved to new 1.0.0 twenty build and reset postgres db.
Now I will recreate all the fields and relations.
So I worried If the problem with field deletion is fixed in the latest builds (1.0.0/1.0.2) or I can face it again any moment?
We have a custom object
Because I can't edit that field, I deleted it and tried to recreate with the new relation type.
However, i now face the error "column customer.buyerId does not exist" and the app crashes.
...
customersbuyerbuyerBecause I can't edit that field, I deleted it and tried to recreate with the new relation type.
However, i now face the error "column customer.buyerId does not exist" and the app crashes.
...
