Error processing

[TrudAX]

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?

[ganroman]

Hello TrudAX. Thanks for your response. In the newer version of LogicApp (which I haven't released yet), I check the execution status of package import. If it's "Partly succeeded", then there is something to look into and a notification mail can be sent to an administrator. Would it be a suitable solution for you?

[TrudAX]

Yes, some notification will be very helpful, thank you.
But what will be a full user story in this case? I am a user, I login to D365 and see some price journals. Before starting working with a journal I need to call an administrator and ask him to check the mailbox?

[ganroman]

Well, in case, when no all price lines were imported correctly, one could mark the price journal with some token (like "*") in the name from out logic app (will try to integrate this one too). I would treat each and every scenario depending on it's severity and situation. What would you suggest, looking forward your feedback

[TrudAX]

ok, imagine you are a user and you see a journal with a "*". Your next question probably will be - what is wrong(for example Item doesn't exist). Then you need to either correct this error(by creating an item and process the file again) or just ignore it. Something like that

[ganroman]

Well, again, depending on scenario, one could try to count number of rows in CSV vs. number of lines in Trade agreement journal. But DIXF integration is always like that: you don't have an immediate control over all lines, you're trying to import. In goes smooth as long as you have a strong data contract