View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006669 | SymmetricDS Pro | Bug | public | 2024-12-06 20:58 | 2024-12-06 21:05 |
| Reporter | pmarzullo | Assigned To | pmarzullo | ||
| Priority | normal | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.14.0 | ||||
| Target Version | 3.15.12 | Fixed in Version | 3.15.12 | ||
| Summary | 0006669: When resolving data by editing the values on the incoming side, null values are lost and replaced with empty strings | ||||
| Description | When a failure occurs or data is in conflict that requires manual intervention on the incoming load side, the user can edit the values that are in the batch to resolve the error or the conflict. When a field has a null value from the batch and is displayed with an empty field on the screen, when the modified values are applied (saved to sym_incoming_error in resolve_data column), the null values are lost and replaced with empty strings instead. We need to preserve the null values. When editing the values to resolve the issue, any fields that were originally null will now have a $(null) value in its place to differentiate it from an empty string value. If you want to put a null value in a field, the string $(null) should be put in the field. An empty string value shows up as a "" in the CSV data of the resolve_data column in sym_incoming_error. A null value shows up as nothing between the commas in the CSV data. | ||||
| Steps To Reproduce | 1. Create a source table with a string column that is longer than the corresponding string column on the target. 2. In the same source table, provide a column that is nullable. 3. Set up synchronization. 4. Insert a record in the source, specifying a value in the string column that is longer than the target can handle, and a null value for the column that can be null. 5. When the incoming batch goes into error, resolve the error by editing the long string value that will fit in the target column, and don't touch the field that has the null value in it. 6. The record will be saved with an empty string instead of a null value. | ||||
| Tags | data sync, ui | ||||
| related to | 0006668 | resolved | pmarzullo | When resolving data by editing the values on the incoming side, null values are lost and replaced with empty strings |
| related to | 0006670 | assigned | pmarzullo | When resolving data by editing the values on the incoming side, null values are lost and replaced with empty strings |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-12-06 20:58 | pmarzullo | New Issue | |
| 2024-12-06 20:58 | pmarzullo | Status | new => assigned |
| 2024-12-06 20:58 | pmarzullo | Assigned To | => pmarzullo |
| 2024-12-06 20:58 | pmarzullo | Tag Attached: data sync | |
| 2024-12-06 20:58 | pmarzullo | Tag Attached: ui | |
| 2024-12-06 20:59 | pmarzullo | Relationship added | related to 0006668 |
| 2024-12-06 21:03 | pmarzullo | Status | assigned => resolved |
| 2024-12-06 21:03 | pmarzullo | Resolution | open => fixed |
| 2024-12-06 21:03 | pmarzullo | Fixed in Version | => 3.15.12 |
| 2024-12-06 21:05 | pmarzullo | Relationship added | related to 0006670 |