In addition to the request regarding an ODBC connection error that was emailed to the support team, we have also noticed some strange behavior after installing version 5.9.7 yesterday.
In several projects that haven’t been modified for a long time, certain columns resulting from cascading merge actions disappear and cause errors.
In the example below, the columns marked with a triangle come from the three previous merges and should not be present in the table where the error occurs.
We will look into it right away. If possible, please share the project via the support email.
In several projects that haven’t been modified for a long time, certain columns resulting from cascading merge actions disappear and cause errors. In the example below, the columns marked with a triangle come from the three previous merges and should not be present in the table where the error occurs.
To clarify, do you mean that the columns are not produced by the merge when they should be, or that the columns marked with a warning sign should not be present in the column selection area? What I am trying to narrow down is whether the column presence validation is faulty or the action itself produced an incorrect dataset.
There was a change in how missing non-key columns are handled in a recent release. Previously, they were silently ignored, but now this causes an error. This means that deselecting (via checkbox) the missing columns, if they should not be present, would have resolved the issue.
So, if I understand correctly, the issue is the validation preventing execution, not a wrong result being produced. Please let me know if I misunderstood anything.
Indeed, I also looked into it on my side, and I think these are leftovers from old developments. Since the previous version didn’t generate an error, we didn’t necessarily notice that the columns were no longer present in the last table shown in the screenshot.
Wouldn’t it be better to have a checkbox in the Merge action — “Fail if selected column(s) not found” — similar to what exists in the Remove Columns action?
In my opinion, anyway, it’s a beter option to raise an error in this case.
