Suggestion for enhancing Cloning and Data Pulling on the EU Platform
Hi,
I've been working a lot on the EU platform and wanted to share a couple of ideas that could enhance the integration experience and reduce potential friction points. Overall, I think the platform is fantastic, but as we all know, there's always room for improvement!
1. Cloning Exports(or Imports..): When cloning an export, whether from the sandbox to production or vice versa, the current process also copies the associated scripts. While this is helpful in some cases, it can lead to duplicated scripts with the same name. To streamline this, could we have an option to disable script cloning? Alternatively, it would be great to have a mechanism that checks if a script with the same name already exists, allowing us to choose whether to use the existing script or create a new one. This would save time and reduce the risk of confusion.
2. Data Pulling and Conflict Resolution: I've noticed that pulling data between environments often results in avoidable conflicts.
For example, when a flow step contains a script with the same name but different IDs, the system prioritizes the ID over the actual script content. This can lead to unnecessary conflicts, especially when the scripts are functionally identical.
Conflicts can also arise from other components, such as field mappings and scheduling times. For instance, if a flow is scheduled in production but not in the sandbox, this discrepancy can trigger a conflict when pulling data, even if the scheduling difference was intentional.
These conflicts often require manual intervention, which seems unnecessary.
To address these issues, it would be highly beneficial to have a more advanced conflict resolution feature that compares the actual content of the flow step—whether it’s scripts, field mappings, or schedules. Such a feature should allow us to flexibly choose which version, code, or mapping to keep and offer the ability to merge changes selectively. This would greatly streamline the process, making it more efficient and reducing the need for manual adjustments.
Lastly, I've noticed that the system sometimes indicates that an exportId exists on the left side but not on the right—can anyone explain why this occurs? See the attached screenshot for reference.
Sometimes, it feels like manually updating the sandbox to match production is faster than pulling, which I'm sure isn't the intended experience.
Conclusion: I believe these improvements could make our work on the platform even more efficient and enjoyable. I'm eager to hear if anyone else has experienced these issues or has additional suggestions. Perhaps together, we can come up with solutions that benefit everyone.
Thanks for your hard work and dedication to continually improving the platform!
Comments
Hi Nuri Ensing
Thank you for your detailed feedback on the cloning and integration lifecycle features.
Regarding cloning, we are looking at a feature that will allow customers to choose between creating a new resource or using an existing one within the environment. I’ll make sure this is captured as an insight.
For data pulling and conflict resolution, we currently rely on the IDs of each resource within the integration. These resources are linked during the initial cloning process, and this link is used later when changes are pulled between integrations. We can’t use names to create this link because names are not unique, and there could be multiple scripts with the same name, which would cause further issues.
To reduce conflicts in cases where field values are expected to differ between sandbox and production (e.g., scheduling, mappings, etc.), we’re introducing a new feature in the August release that will allow users to selectively merge changes between integrations. This feature lets users choose certain fields to ignore when pulling changes, helping to prevent conflicts. I’ll share more details on this once the release is out.
I’ll also follow up on the export ID issue after we’ve done some research to understand why this is happening.
Thank you again for taking the time to provide your feedback. It’s greatly appreciated.
Wooo!!
Niiiiiiicee =)
Thanks for your detailed answer Praveen Kumar Reddy Basani
Please sign in to leave a comment.