Skip to content

[Bug]: [Tech-Debt] On updating the datasource name, the actions associated with it doesn't get the updated datasource name #40292

@NilanshBansal

Description

@NilanshBansal

Is there an existing issue for this?

  • I have searched the existing issues

Description

Since each action in the database maintains a copy of the datasource object, when the data source object is updated, it is only reflected in the data source collection and not downstream in all the actions that maintain the copy of this datasource.

Now, since the datasource can only be updated with the name property, it is not an issue from the functionality perspective. Still, it is a data inconsistency issue in the database, and therefore, this issue should be treated as a tech-debt.

The client side functional display will be resolved with this issue: #40287

Steps To Reproduce

Create a new data source and create multiple actions on top of it. Now update the data source name and check the mongo database for each action. You will see the data source name in the action is the old one and not reflected as the new one.

Public Sample App

No response

Environment

Production

Severity

Low (Cosmetic UI issues)

Issue video log

No response

Version

Cloud v1.68

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingIntegrations PodIntegrations Pod GeneralIssues related to the Integrations Pod that don't fit into other tags.Integrations ProductIssues related to a specific integrationLowAn issue that is neither critical nor breaks a user flowNeeds TriagingNeeds attention from maintainers to triageProductionQuery Widgets & IDE PodAll issues related to Query, JS, Eval, Widgets & IDETech DebtIssues or Tasks which are tech debts

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions