Welcome to the Syniti Ideas Portal!

Do you have feedback regarding the current product, or new ideas for improvement?

Tell us how we can make the Syniti Knowledge Platform more useful to you.

Planned

Replicate generating files in UTF-8 format

at Loreal, we are required to generate output files for certain objects as part of data migration process. These files have to be in UTF-8 encoding only. But when we try to generate the files using replicate, they are getting generated with UTF-8 BOM encoding not UTF-8. This is causing the client additional manual effort in converting them to UTF-8. please see the feasibility of adding this feature to replicate

Sudhakar Reddy About 2 months ago

Planned

Provide option to download high cell-count Excel files in Migrate

Creating this in response to Support Request (#80785). We have some very wide datasets (SalesForce) into the hundreds of columns, with not terribly large row counts of 100k-200k. Upon attempting to download, Migrate “spins” attempting to produce a downloadable excel, but times out at exactly 3 minutes without any error or result. Is there an alternative option that could be used to push this Excel generation to a background job to avoid the front-end timeout? Contact Rodney.Bonham@syniti.com for any additional questions.

JOHN SLAGLE 2 months ago

Planned

System Datastore import / export format needs alignment

The template “Import Tables” requires the following column order: SCHEMA,NAME,TYPE,DESCRIPTION,TAGS The Export > CSV feature downloads the following order: "Name","Description","Type","Schema" If both are in the same order, then no manipulation is required if someone wanted to copy a table list from one datasource to another.

Ana Garcia Rubio (Syniti) 2 months ago

Future Consideration

In SST/MDM Option to delete a user should be limited to a specific role or security level where the initial creation of a new account does not work correctly

The system security functionality has an option to delete a user from the system. The option to delete a user should only be used in cases where the initial creation of a new account does not work correctly, and the user needs to be deleted and immediately recreated, otherwise the standard deactivation process should be used. User should not be allowed to be deleted with historical information.

Randall Dunn 3 months ago

Planned

Remediation Info

Next to the release toggle for remediation add some kind of button to allow the user to go into a report or some kind of visual representation of what remediations are associated with that release and the status of the individual remediation. The report, target and other helpful information should be listed. This gives the PM an overview of how much remediation is being used and where it is being used.

Derek Williams 3 months ago

1

Unlikely to Implement

Remediation Improvement

Remediation can be further simplified by having an option in the report to turn on remediation and provide a value. Then in the background the report is updated in SQL with the value provided and the user does not have to go into SQL. If the logic is more complicated then the user can go into SQL and update. The remediation value would then be visible in the UI for the report

Derek Williams 3 months ago

1

Planned

Include Primary Key Details in "Record Not Found" Error Messages

Currently, when Replicate encounters errors like: Record to update not found in target table Record to delete not found in target table …the error messages do not include the primary key (PK) or identifying field values of the missing records. This makes it difficult for users to troubleshoot or trace the problematic data, especially in large-scale environments. Suggested Enhancement: Include the PK values in these error messages—similar to how duplicate key errors already include them (e.g., Duplicate Key: [PK Field1=..., Field2=...]). Benefit: Easier debugging Improved traceability More consistency across error reporting Can this be considered for a future update?

bloodomsin 3 months ago

Personal Identifiable Information and sensitive information tagging through metadata scanning and profiling

Utilize existing open source libraries ( https://microsoft.github.io/presidio/structured/ , https://pypi.org/project/pii-Scanner/ , or similar) to identify columns likely to contain PII during the metadata scan or profiling, and then add tags to the data element to allow clients to filter and flag columns that may require additional handling or security. This could also allow for tagging for the type of data like phone numbers, emails, address data, or more. This is an extremely common request we get from clients when demoing Catalog, metadata scanning, and profiling. This data could then be carried over into snapshot management, dataset design, mapping, and reporting in Migrate.

Tyler Triemstra 3 months ago

Planned

Multiple Environment Reporting

When using multiple environments in Migrate there are limited to no indicators to users as to what environment they are looking at. For example, follow the steps below: Go to Validate > Migration Reports Click Dev > Switch to an another environment (i.e. Mock 1, DR, LOAD, etc.) After doing this, the screen will say ‘Mock 1’ at the top and be in a different color, which is great. If you go into the report list for a dataset, the Mock 1 ribbon continues to be present. But when you click the preview button to look at the contents of the report, the ribbon and colors are gone and it looks like just any other report. It would be great if the ribbon existed on this screen too to make it clear to users what they are looking at, to be able to screenshot and attach to test cases, etc. In addition, when you download a report it looks just like any other report downloaded from DEV. These downloaded reports should have a different color in the header rows (based on the color assigned to the environment in setup), and the file name should also be versioned to include the environment in it.

Peter Berke 3 months ago

1

Planned

System Report - MIG table field to add

We have a couple of enablement projects going on and, to help on the code review, we are creating some SYS reports using MIG_ tables available in the srcconstruction database. However, we have noticed that we can’t find some fields, so I’d like to check if it would be possible to add them in one of the tables below: MIG_INTERFACE_SOURCE_ENV MIG_ALL_DATASETS If so, the fields are: Developer (mapping→ release dataset) and Short Name (dataset design), please see attached. Thank you, Ana

Ana.Castro 4 months ago

Future Consideration

Report Fields Consistency

The usage of various fields with respect to Migration Reports is not entirely consistent across ADMM. For example, when saving a report that is flagged as an ‘Error’ Report Type, you get a warning about filling out the Business Impact and Recommendation fields, which makes sense. But as far as I can tell, those fields are not user-facing in both Migration Reports and Deployment Reports. The fields are not available in the ‘Choose Columns’ section when looking at all reports, and they do not show when you drill into the details of any individual report. Another example is Report Priority. ADMM has values provided natively such as Major, Minor, Critical, Info, etc. These all make sense and can be very useful for cleansing. But, this field isn’t available anywhere in Migration/Deployment Reports, and it also isn’t available in the Report Import Template, making it nearly impossible to actually use. It would be great if all the fields available when adding reports (Priority, Impact, Defect # etc.) were 1) available as a column to choose from in Migration/Deployment Reports, 2) showed in the details when you click into a specific report from Migration/Deployment Reports, and 3) were available in the Report Import Template.

Peter Berke 4 months ago

1