Skip to content

145 use case creation doesnt recognise selected dataset and doesnt proceed to publish - #423

Closed
UdayRajSahai2 wants to merge 3 commits into
devfrom
145-use-case-creation---doesnt-recognise-selected-dataset-and-doesnt-proceed-to-publish
Closed

145 use case creation doesnt recognise selected dataset and doesnt proceed to publish#423
UdayRajSahai2 wants to merge 3 commits into
devfrom
145-use-case-creation---doesnt-recognise-selected-dataset-and-doesnt-proceed-to-publish

Conversation

@UdayRajSahai2

Copy link
Copy Markdown
Collaborator
  1. Fixed the issue in which different usecase data was coming in new usecase
image
  1. Usecase details persisting . Earlier Running status was showing default value even though i have changed it
image
  1. Dashboard data persisting
image
  1. Dataset data is also persisting
image
  1. Contributors data is also persisting
image
  1. It is letting publish now
image

queryClient.setQueryData(queryKey, (old: any) => ({
usecaseDashboards: [...(old?.usecaseDashboards || []), newDashboard],
}));
},

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of setQueryData you should use queryClient.invalidateQueries({ queryKey });
for ex:
collabratives/edit/details/page.tsx

@Abhishekfm

Copy link
Copy Markdown
Contributor

for keeping cache in sync after save/add/delete, use invalidateQueries({ queryKey }) for that page’s query and let the form rehydrate from the refetch. And invalidate only the query this page owns.

@Abhishekfm

Copy link
Copy Markdown
Contributor

Closing this PR, as this issue is resolved here #432

@Abhishekfm Abhishekfm closed this Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants