Great article Roman/Ludwig. Thanks for sharing. Only issue was that forms were a bit “blurred” (in azure) and not really readable. But I followed the logic ok. I’m keen to try this stuff in my test environment. Has got so many possibilities, not just for integrations but also for taking away lots of manual/error prone procedures in data migration testing. Joe
That looks good, but how do you work with validation errors? Like you import file with 100 lines, execute data project for it, then 3 lines don’t pass validation(for example – item not found) and you will have a journal with 97 lines as a result. How do you notify a user that this journal doesn’t contain all lines from the file?
Hi Denis, Will pass your question along to Roman who can answer you best. Would be great if you could provide an email to which we can send/share the answer to. Many thanks, Ludwig
Great article Roman/Ludwig. Thanks for sharing. Only issue was that forms were a bit “blurred” (in azure) and not really readable. But I followed the logic ok. I’m keen to try this stuff in my test environment. Has got so many possibilities, not just for integrations but also for taking away lots of manual/error prone procedures in data migration testing. Joe
LikeLike
That looks good, but how do you work with validation errors? Like you import file with 100 lines, execute data project for it, then 3 lines don’t pass validation(for example – item not found) and you will have a journal with 97 lines as a result. How do you notify a user that this journal doesn’t contain all lines from the file?
LikeLike
Hi Denis, Will pass your question along to Roman who can answer you best. Would be great if you could provide an email to which we can send/share the answer to. Many thanks, Ludwig
LikeLike
Thanks Ludwig. I put the question on Roman’s GitHub – https://github.com/ganroman/D365FO_DIXF_ZipPackage/issues/1
LikeLiked by 1 person