fix:Prevented duplication of trip sheets when re fetching in monthly consolidation trip sheet#1461
Merged
MhmdSinanKT merged 1 commit intodevelopfrom Mar 27, 2026
Merged
fix:Prevented duplication of trip sheets when re fetching in monthly consolidation trip sheet#1461MhmdSinanKT merged 1 commit intodevelopfrom
MhmdSinanKT merged 1 commit intodevelopfrom
Conversation
…consolidation trip sheet
MhmdSinanKT
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature description
Need to: Prevent duplication of trip sheets when re fetching in monthly consolidation trip sheet
Solution description
Prevented duplication of trip sheets when re fetching in monthly consolidation trip sheet doctype
Output screenshots (optional)
Screencast.from.27-03-26.12.27.37.PM.IST.webm
Areas affected and ensured
Monthly consolidation trip sheet doctype
Is there any existing behaviour change of other features due to this code change
No
Was this feature tested on these browsers?