Enhanced Feature Request: Replication-Standard-Aware EXP View Generation

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