Overview Syniti currently allows views to be generated, but the generated views are not fully aligned with the standards required by the replication process. As a result, developers must manually enhance the generated views before they are usable in the broader migration and replication framework. This feature request proposes enhancing the existing view-generation capability so that generated *_T_EXP views are not only structurally created from metadata, but are also aligned to the required replication standards from the start. The goal is to reduce manual rework, improve consistency, and ensure generated views are closer to production-ready. Current Gap The current generated views provide a useful starting point, but they often require manual updates to align with replication and migration development standards. Common manual enhancements include: adding required ETL/control fields applying standard null-handling logic applying consistent data type defaults aligning column order to expected target structures applying standard aliases adding source/reference fields including required legacy key fields ensuring generated fields match replication expectations applying consistent formatting and naming conventions adding object-specific joins or placeholders handling required fields that are not present in the source structure validating that generated output is compatible with downstream replication processes This means the generated views are helpful, but they are still incomplete from a developer productivity perspective. Proposed Enhancement Enhance the view-generation framework so that generated *_T_EXP views are built using configurable replication standards. The generator should not only ask: What columns exist in the target structure? It should also ask: What does the replication framework require this view to look like? The generated output should include standardized logic for: required control fields key fields default values data type handling nullability handling expected source aliases standard comments and section dividers target column ordering placeholder expressions for unresolved fields generation reasoning for each output field Example

maxtitov 3 days ago

1

Replicate

We would like to request a few usability enhancements in the PostgreSQL Editor – Results section, based on our day‑to‑day usage. Observations / Current Limitations In the query results section, the horizontal scroll bar is only visible when scrolling to the very bottom of the page. This makes it inconvenient to view wide result sets with many columns. There is no option to copy multiple selected columns or the entire result set at once, unlike standard SQL editors (e.g., pgAdmin, SQL Developer). Currently, copying data is limited and time‑consuming for analysis and sharing. Requested Enhancements We request the following improvements in upcoming releases: Always‑visible horizontal scroll bar (or a fixed scroll bar at the top of the results grid) to easily navigate wide result sets. Ability to select and copy multiple columns, multiple rows, or the entire result set in one action. Option to copy results with column headers. These enhancements would significantly improve productivity and align the PostgreSQL editor experience with commonly used SQL tools. Please let us know if any of these features are already planned, or if additional inputs are required from our side. Thanks, Srikanth Vavilala

Srikanth Vavilala 6 days ago

1

Migrate

create a report which can show the Audit logs. Project team needs to see who has changed the mapping/dataset/rule in Syniti ADMM on which date and time or let us know if any report is available which can show the audit logs. Let us know if any existing report is available in your point of view! Project Release Dataset Changed By Change Description or artifact Changed on (date and Time)

Arun Sasi Maliyakkal 7 days ago

7

Migrate

We need a migration execution statistics report. Below is the format of the report which will give execution statistics of a data migration object. KPI report should look like below Purpose: This report will give overall effort and time spent on an object. Project Release Dataset name Subject area Execution date ETL tasks Run time in seconds Records processed Status BBM BBM_WB open po S2P 06 10:00 ekko 25 21312 ok open po 06 10:00 ekpo 30 213123 ok

Arun Sasi Maliyakkal 7 days ago

2

Migrate

Text Qualifier, Add Transactional Info, and Include Header Row are all features in the Migrate ETL Task, but not Replicate.

jay.hornback@syniti.com 8 days ago

Replicate

When adding Sources or Replications within Replicate Preview, it defaults Index = 1000 no matter what already exists. It should behave similarly to the rest of ADMM where it will +10 the max Index value.

jay.hornback@syniti.com 8 days ago

1

Replicate

Summary Introduce a lightweight, non-invasive UI enhancement layer that improves how users interact with and interpret data within the existing platform. This solution overlays additional visual cues, intelligent filtering, and usability improvements without modifying the core application. Problem Statement Users working within the current interface face several friction points: Difficulty quickly identifying key data signals (errors, flags, statuses) High cognitive load when scanning large datasets or dropdowns Inefficient navigation due to lack of smart filtering or prioritization Repetitive manual effort to interpret or locate relevant information This results in: Slower task execution Increased risk of oversight or error Lower overall user efficiency and satisfaction Proposed Solution Implement a client-side enhancement layer that augments the existing UI with: 🔹 Visual Enhancements Dynamic color coding for key fields (e.g., status, errors, boolean flags) Priority-based highlighting (e.g., TRUE/FALSE overriding other styles) Improved contrast and readability for dense data grids 🔹 Intelligent Interaction Smart dropdown filtering with fuzzy/wildcard search (e.g., PMWC*CRCO) Auto-suggest top matches with preview lists Keyboard-driven selection (Enter to select best match) 🔹 Real-Time Responsiveness Lightweight refresh logic tied to DOM updates (MutationObserver-based) Efficient rendering using throttling (e.g., requestAnimationFrame) Adaptive updates as new data loads dynamically 🔹 User Productivity Features Quick-select panels for common values Reduced need for scrolling and manual searching Faster identification of actionable data Use Cases Data migration validation (preload/postload analysis) Error identification and remediation workflows Dropdown-heavy configuration tasks Large dataset navigation and filtering

maxtitov 8 days ago

Migrate

Eli Lilly is submitting feedback that they would like to install the new “Websocket” Connector on an application disk (for example, "D" drive instead of "C"). We see at least 2 paths being used with no option during install to change them. Can you please allow for customizing these 2 paths? Connector "Install" path - C:\Program Files\Syniti\Syniti Connector Connector "Log" path - C:\ProgramData\Syniti Connector\logs “Websocket” Connector EXE - https://files.syniti.com/f/skpconnwin100

Ben Bauer 12 days ago

1

May 8

Platform

It would be awesome if we could interact with a client's SFTP server from Syniti Drive and/or Cloud Replicate. For example, a client might wish to move files securely from their SFTP server into Syniti Drive, so that Cloud Replicate can import the files into the Migrate or Construct working database. Or a client might wish to take data in their working database and write it out to a file in their SFTP server (either directly from Cloud Replicate, or indirectly from Syniti Drive). I suppose another way of framing this would be enabling Syniti Drive to act as an SFTP server that the client can connect to.

Ben Bauer 12 days ago

1

Jul 31

Replicate

Customer has around 320 users across more than 27 deployments. Current UI admin is time-consuming and inefficient (many manual steps). Request: bulk edit or bulk import feature

Guillaume Dutey 12 days ago

3

Migrate

+1

I have a rule that has been deactivated. The last time it was executed it errored. I don’t want to spend any time on fixing the rule as it is no longer used (we can’t delete it because it’s one of the auto-generated rules). I’d like to be able to clear out the error message to avoid the distraction.

jay.hornback@syniti.com 13 days ago

1

Migrate

In Syniti ADMM, there is no built-in version control mechanism for mappings and ETL components. As a result, any changes made at the UI level are not versioned or historically tracked, making rollback or recovery through the UI infeasible in case of code loss, corruption, or unintended modifications. Due to this limitation, recovery cannot rely on application-layer features and must instead be handled at the database level. This includes maintaining backups or scripts of underlying objects such as mappings, transformations, and ETL logic stored in the database. Client is looking for a feature where the versions can be controlled for Mappings and ETL components in ADMM

Sharmistha Sur 13 days ago

1

Migrate

I have 3 targets within my dataset. I’m publishing report #10 for all three, so you see index #10 3 times. I would propose we either refactor the index numbers to be unique, or display ‘target’ column so that the auto-sort goes by target first, then index.

jay.hornback@syniti.com 14 days ago

1

Migrate

Currently we have a setup under Admin>Parameter to control the automatic download reports as CSV when the number of records exceed 1 million. However, having this control at the report level would help save time when we work with systems like SuccessFactors where the export should be in csv format and not xlsx. Something like default format flows down from Parameter page to all reports and developers have option to overwrite the format to change the type to CSV.

Santhosh Thoutam 14 days ago

1

Migrate

There are a lot of things here that I think could be improved: 1) Sort the recurrence dropdown properly: monthly/weekly/daily/hourly 2) Add a recurrence of ‘one time/specific date’. ie: I want to execute a job one time in the future, on a specific date (calendar picker) 3) For Recurrence = Monthly, when = Specific Date, you can choose values 1-31. I’m not sure how valuable this is. What if I chose the 31st? Only 7 months have a 31st day…

jay.hornback@syniti.com 18 days ago

2

Replicate

When we update ZACTIVENEW, we should also always update ZINACTIVE_REASONNEW at the same time. Can the auto-generated shell of this update view from ADMM also include a placeholder for ZINACTIVE_REASONNEW?

emily.burnside 18 days ago

1

Migrate

When copying the ETL structure in ADMM, allow for more granular selecting of parts of the Dataset Transform. Example: I have an object with 34 tables and 1000+ update rules in Dataset Transform. I have changed the Target Transform for 1 table and I want to copy that change from Dev to Mock 2. There is currently no option to only copy the ETL for one table in the Dataset Transform, I am forced to copy the entire Dataset Transform. With the size of the object, this takes 15+ minutes to complete. Could this be improved to allow selecting specific Target Transforms to copy from the Dev ETL?

emily.burnside 18 days ago

1

Migrate

Some examples of current challenges: The current process is managed in a static pop‑up window. The Sources replacement step requires to manually update potentially dozens of target entries within the pop‑up, instead of substituting the source, e.g., ECC_US to ECC_EU. It does not allow copying by blocks, i.e. a full copy is the only option. Even if the job fails, a new release may be partially created. Idea for improvement: dedicated section for release copies including: Configuration and preview side by side Allow execution by blocks, e.g. copy by subject area, by dataset Dataset design copy decision, i.e. create a new datasets or reuse Process monitoring Backend code support Releases comparison post copy: datasets, mappings, reports, ETLs, code… This section could also manage additional features related to development reusability within Migrate.

Ana Garcia Rubio (Syniti) 18 days ago

1

Migrate

In Dataset Design there is a "Technical field" column in Data Elements Tab. It helps to identify which table each data element refers to - especially when various rows have same name value. When performing Dataset Bulk Edit, this column is not displayed, resulting confusion accross rows with same name value. Idea: add this non-editable column to Bulk edit screen

Guillaume Dutey 20 days ago

3

Migrate