Bug Report: Related Record Field Not Updating in Tasks Table After Project Name Change

[tglatt]

Product: Softr - Native Database (new) with Custom Front-End Application

Application Type: Project Management System

Issue Description:

When updating a project name via the front-end application’s “edit record” functionality, the primary field (Project Name) in the projects table updates correctly. However, the corresponding related record field in the tasks table, which links tasks to projects, does not reflect this change. This leads to tasks becoming unlinked from their parent project in the front-end, making them appear to “disappear” from the project view.

Work Context:

The application is a project management system built on Softr’s new native database. It utilizes the following tables:

• projects
• clients
• people
• tasks

The projects table has a primary field named Project Name. This field is a formula field that concatenates two other fields from the projects table: client and name (where name is the basic, editable name of the project).

Steps to Reproduce:

1. Identify a Project: Select an existing project in the front-end application that has associated tasks.
2. Access Edit Record: Navigate to the “edit record” option for this project in the front-end.
3. Change Project Name: Modify the name field (the basic project name) of the selected project.
4. Save Changes: Save the updated project record.
5. Observe projects table: Verify in the Softr native database that the Project Name formula field in the projects table has correctly updated to reflect the new concatenated name.
6. Observe tasks table: Check the tasks table in the Softr native database.
7. Observe Front-end: View the project details page in the front-end application for the modified project.

Expected Behavior:

• Upon editing and saving the project’s name field in the front-end:

• The Project Name formula field in the projects table should update correctly (which it currently does).

• The related record field in the tasks table (which links tasks to projects) should automatically update to reflect the new Project Name from the projects table, maintaining the correct link between tasks and their parent project.

• In the front-end, all tasks previously associated with the project should remain visible and correctly linked to the updated project.

Actual Behavior:

• After editing and saving the project’s name field in the front-end:

• The Project Name formula field in the projects table updates correctly.

• However, the related record field in the tasks table retains the old, unchanged Project Name.

• Consequently, in the front-end, all tasks that were previously linked to the project appear to “disappear” from the project’s view because their related record field no longer matches the updated Project Name in the projects table, effectively breaking the link.

Impact:

This bug severely disrupts data integrity and user experience. Users lose visibility of tasks associated with projects they have renamed, making the project management system unreliable and leading to potential data loss or confusion. It prevents effective project tracking and management within the application.

[tglatt]

I expected this, but confirmed that this behavior happens when making the same changes directly in the database.

[Zorro]

+1

Perhaps this is the same issue? But I have experienced this where changing the primary field in the table to another field does not update the name in the related record.

[artur]

@tglatt just to confirm are you saying the the same issue exists in the database as well when you update via studio ?

We will need a collaborator access to check it as there is a chance the linking is broken

[artur]

@Zorro the one you mentioned is a different one we will check too… So you change the primary field and linked record still shows the old primary field value is that correct ?

[Zorro]

Correct. The label variable does not change.

Perhaps I should create a seperate bug report, I apologise. But I also just came across that the names are not consistent across linked records / lookups / formula fields. Here is an example of where this occured. Firstly, I was trying to create a related record & lookup in Table A to Table B and it worked fine. Then in Table B tried creating related record to Table A and a lookup, it worked. But when creating the lookup in Table B, the related record field was created one more time, so I deleted it. I think thats what causing this issue. Then in the dropdown there were blank spots… See screenshots. I can try to recreate this again with exact steps if you are unable to recreate. Original name was “Zorro Fox”

Table A

After this, I tried deselecting the record and selecting again in Table A. These are the results: Full Name does not show in table view, and for the selected record in dropdown. See Screenshots

Again… after this I went back to Table B, and reassigned the Table A linked record, went back to Table A, and name was fixed without changing anything in Table A.

[artur]

@tglatt we identified the issue with formula field being lookup value… we will roll out a fix soon

[artur]

@tglatt this is fixed… please let me know once you check… and thanks for reporting it

[tglatt]

Sorry not to confirm earlier, but the earlier issue appears to have been fixed. Thanks!