Build better products with our product team
I’ve been using Sync to pull from MS SQL Server, from a couple of different sources that have either CDC or Change Tracking enabled.Occasionally, there is some kind of hiccup where things get out of sync. There are changes in the source that never replicated, but Sync thinks it’s already processed them, so it doesn’t try to catch up.For CDC-based jobs, I’d like an option to “Run with Resync”. Supply a date, and have that be used as the basis point for Sync to look back. Not whatever high water mark is stored in the internal Sync database.It would be OK if it applied the same look-back date to all the Tasks in the job. It would be just for that one job execution.
Instead of writing SQL to generate custom queries it would be amazing if I could write prompts via an AI tool to generate the output for me. This would be especially helpful if members of my team weren’t knowledgable with SQL code.
I’d like to change the order of the Tasks within my Job. Seems like the easiest way to do this within your existing UI, would be to add under the “. . . “ hover menu (on the Task tab), an “Move Up” and “Move Down” option.
While looking at the details of a Job (job-details.rst), I’d like to have a tab for “Transformations”. This would show me a list of transformations that are triggered when this job or its tasks run. Clicking on the transformation would bring me to the transformation details page.
It would be super cool if the underlying metadata and job/task history (in the internal Derby database) were available to be queried.The simplest way to do this might be to replicate the internal database (using Sync!) to some other customer-owned database. Then they can access it using their connectors and tools of choice.So someplace under “Settings”, the user would provide connection details for “Reporting Database”. Then a hidden Sync job would sync up the internal database to that destination every X minutes or hours.I guess a different way to accomplish this would be for me to access all of the data through the Sync API, and set up a API-to-database syncing job myself. But that’s more work for me. ;-)
When viewing the details of a Task (task-details.rst page), I’d like to see a tab for History.That would show me the date times and, more importantly, the volumes, of that table that was loaded over the last N days.
Launch CData product-specific certifications with curated learning paths and trails to uncover and learn different aspects of each CData product. Users can have milestones and badges available for the learning paths they completed like:CData Sync Rookie > CData Sync Learner > CData Sync Ranger > CData Sync Expert > CData Sync Veteran Organizations can have their users take certification exams on product knowledge and have certified individuals in their teams.
What if there was a way to select which data points being fetched is PII and it automatically masks that data from source to destination?To take it to next steps, what if the application had a learning model to learn which data is PII using user inputs?
It would be convenient if we could Disable temporarily a Task within a larger Job, rather than having to Remove it entirely.
📢 Exciting Updates from CData Sync! Q4 2023 Release Highlights 🌟 We're thrilled to announce the latest features in the Q4 2023 CData Sync release! Here's a quick snapshot: API Connector - Seamlessly connect with any API without coding. Perfect for users of all technical levels. Continuous Replication - Quicker, point-and-click replication options for near real-time data access. No more complex setups! Integration with Databricks Unity Catalog - Embrace unified data governance by managing assets across all platforms efficiently. 🔗 Dive deeper into these updates in our Q4-2023 Sync Release Blog. 🎥 Want a visual guide on the API connector? Check out our instructional video here. 📄 For an in-depth look at all new features, head over to our Current Release Documentation. Ready to experience these features? 🆓 Try them out with a Free Trial. Already a CData user? Upgrade now and elevate your data management game! Cheers to continuous innovation! 🚀 The CData Sync Team
When an Error occurs, sometimes we want to acknowledge the error and hence clear it from the Error status, but still have a record that the errors has occurred.For example, a connector which failed to pick up email due to a temporary connection issue, may show an error, but subsequent runs are okay. The connectioin has recovered. We currently have two options:Delete the Error - now we can’t see how often the connection fails. Do nothing, but now we accumulate errors and we don’t know if we have reviewed them or not.Being able to put the Error into an Acknowledged state would be useful.
When importing an arcflow file it’s often useful to be able to disable it immediately.Currently this means turning off Send on the relevant connectors’ Automation tabs. It would be useful to be able to disable any workspace quickly.Also it would be useful to be able to export a workspace with connectors disabled, so they are safe when being re-imported
It would be great if I could search for things across the application from ANYWHERE within the application so I can get to what I’m looking for faster. For example: my connections, the tables/views that originate from them, or the custom derived views/saved queries I create inside the Data Explorer.
Ability to export selected connectors as text, containing Workpace, Connector ID, Connector Description etc so that it can be used as documentation elsewhere. HTML format would be good
It would be useful to have more space for comments and documentation, including change notes in connectors. Perhaps this could sit on its own tab. Maybe the connector could have a small indicator (like cells in an Excel sheet) when there is a comment. Maintenance and change history are key to developing flows.
We have a common scenario where we receive orders by email daily at 09.30.To avoid having to check each morning that we received an order and it was processed correctly, we’d like to have something that monitors if a connector does NOT process a message for say 25 hours.Ideally we’d like to be able to put that logic on any connector. It might be that the order wasn’t received, or the order didn’t get all the way through the flow.In the meantime, we will also look into using Nagios to monitor the Sent folder on particular connectors.
A lot of applications today have a dark mode option for users who prefer that UI. It would be great if Connect Cloud introduced this as a theme that they could enable in their settings.
I’m currently a query user and only have access to connections that an admin users grants me permission to perform specific query actions to. I often have to contact the system administrator to grant me access to connections that exist in our account but it would be easier if I could do it directly within the application.
I have a member on my team who is color blind. This can often create an issue of seeing contrast across components on the page or understanding status colors unless there are icons that help identify the message at hand. It would be great if there was a color blind mode so that there was greater contrast across these elements on the page in addition to being able to easily identify when different colors are being used for different purposes.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
