Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
NilanshBansal opened this issue Apr 17, 2025 · 0 comments · May be fixed by #40293
Assignees
Labels
Bug Something isn't working Integrations Pod General Issues related to the Integrations Pod that don't fit into other tags. Integrations Pod Integrations Product Issues related to a specific integration Low An issue that is neither critical nor breaks a user flow Needs Triaging Needs attention from maintainers to triage Production Query Widgets & IDE Pod All issues related to Query, JS, Eval, Widgets & IDE Tech Debt Issues or Tasks which are tech debts

Comments

@NilanshBansal
Copy link
Contributor

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

@NilanshBansal NilanshBansal added Bug Something isn't working Integrations Pod General Issues related to the Integrations Pod that don't fit into other tags. Integrations Pod Integrations Product Issues related to a specific integration Needs Triaging Needs attention from maintainers to triage Query & JS Pod Issues related to the query & JS Pod Query & Widgets A dummy placeholder to fix the corrupted github actions config json Query Widgets & IDE Pod All issues related to Query, JS, Eval, Widgets & IDE labels Apr 17, 2025
@NilanshBansal NilanshBansal self-assigned this Apr 17, 2025
@Nikhil-Nandagopal Nikhil-Nandagopal added Low An issue that is neither critical nor breaks a user flow Production labels Apr 17, 2025
@github-actions github-actions bot removed Query & JS Pod Issues related to the query & JS Pod Query & Widgets A dummy placeholder to fix the corrupted github actions config json labels Apr 17, 2025
@vivek-appsmith vivek-appsmith added the Tech Debt Issues or Tasks which are tech debts label Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Integrations Pod General Issues related to the Integrations Pod that don't fit into other tags. Integrations Pod Integrations Product Issues related to a specific integration Low An issue that is neither critical nor breaks a user flow Needs Triaging Needs attention from maintainers to triage Production Query Widgets & IDE Pod All issues related to Query, JS, Eval, Widgets & IDE Tech Debt Issues or Tasks which are tech debts
Projects
None yet
3 participants