When using the Migration Center validation tool, the error messages are often very vague and provide little context as to where to begin debugging validation issues. It would be great if there were line numbers or additional information in the error message to make writing validation logic easier.
For instance:
TransformationError Potential Error types
s [Error]: Action 'map' unable to process value at path ANS.content_elements, check your target from source and parameters to resolve
There are 30 objects in the layout array I'm migrating to be the content_elements array, consisting of more than ~650 lines of JSON metadata in addition to the ~460 lines of actual migration mapping logic. The error doesn't say which one is causing "Action 'map' to be unable to process ANS.content_elements", nor does it say if the issue is from the source or parameters.
My mapping logic uses JMESPath to conditionally migrate certain elements and that in and of itself is difficult to debug, so to have such little information in the Migration Center interface compounds that greatly. The Migration Center error doesn't tell me if my JMESPath conditions are failing, if there's inconsistency in the source data, if the migration logic is improperly formatted, nor which line is triggering the error.
I've encountered other errors that have left me scratching my head for hours just to discover that I've got a typo or I'm missing a character somewhere.
Considering the migration process is mandatory given the deprecation of the Inbound Partner Wires, it would be super helpful to have more accurate and detailed error messages while validating migration mapping logic.
Thanks for taking the time to consider this idea.
