Duplicate deal date change
Hi,
If anyone encountered this issue and found a work around I'd be happy to hear it.
The situation is as follows -
I made an automation that created a duplicate deal when I mark and existing deal as Won.
I need the duplicate deal's expected close date to be set to a year from the original "Expected close date", but the automation sets it to a year from the day I marked as Won.
Any solution?
Answers
-
You can do this only using Make/Integromat or Zapier.
0 -
I can help with this.
0 -
I'm also encountering this issue with an automation I created that duplicates a deal when marking an existing deal as Won. My goal is to set the duplicate deal's expected close date to be one year from the original "Expected close date." However, the automation sets it to be one year from the day I mark the deal as Won instead. If anyone has encountered a similar issue and found a workaround or solution, I would greatly appreciate hearing about it. Thank you!
0 -
I'm experiencing an issue with an automation I created to duplicate a deal when the original deal is marked as "Won." My goal is to set the expected close date of the duplicated deal to be one year from the original deal's expected close date. However, the automation currently sets the new expected close date to be one year from the date the deal is marked as "Won." If anyone has encountered a similar problem and found a solution or workaround, I would greatly appreciate your advice. Thank you!😊
0 -
To manage a duplicate deal date change, first identify the affected deals within your system. Ensure you have a backup before making any changes. Update the deal date by either modifying the existing entry or merging duplicate entries while retaining the accurate information. Use automation tools or scripts to streamline this process, minimizing manual errors 😶. After changes, verify the updates by cross-referencing with original data sources. Communicate with relevant stakeholders to inform them of the changes and ensure alignment. This approach helps maintain data integrity and improves overall workflow efficiency.
0 -
To change the deal date for duplicate entries, start by identifying the duplicates in your database or CRM system. Use filters or queries to locate deals with the same date and relevant identifiers. Once identified, decide on the new date for the duplicate entries, ensuring it aligns with your business logic and does not conflict with other records😍. Update the deal date field for each duplicate entry, either manually or through a batch update process if supported by your system. Finally, verify the changes to ensure accuracy and consistency across your data. Regularly monitor for duplicates to maintain data integrity.
0 -
It sounds like your automation is creating a duplicate deal effectively, but the expected close date isn't syncing as intended 😀. Setting the duplicate deal's expected close date based on the original "Expected close date" rather than the date it was marked as Won seems crucial for maintaining accuracy in your workflow.
0 -
I encountered a similar issue before. You might want to adjust your automation logic to calculate the duplicate deal's expected close date based on the original 'Expected close date' rather than the day it's marked as Won. This should ensure it reflects the intended timeframe accurately Thanks 🤗
0 -
Its really frustrating I was facing the same issue. I wish it may solve. Best Wishes 🤗
0 -
I’m having trouble with an automation I set up to duplicate a deal when it’s marked as "Won." I want the new deal’s expected close date to be exactly one year after the original deal’s close date, but right now, it’s setting it one year from the date the deal is marked as "Won." If anyone has dealt with this and has a solution or workaround, I’d really appreciate your help. Thanks! 😀
0
