39

When inbound messages fail to process it's really helpful to view the incoming file to see if there are any major issues.  Without the ability to access the file, it's really hard to troubleshoot. This was possible in previous versions of AX through AIF and was frequently used by our clients.  

Category: Data Management
STATUS DETAILS
Under Review

Comments

J

Hi all,

I think it is possible to implement a small extension for the Recurring queue form to able to download the original file which was sent. Please see my sample code on this link :
https://github.com/istvan2molnar/D365FO-Extensions/tree/DMF_RecurringFileDownload

Deployable package is also available if you just would like to install and try (Build server was Version10 PU24):
https://github.com/istvan2molnar/D365FO-Extensions

Hope you will find it useful, take a look and let me know your thoughts!
Thanks!

Category: Data Management

J

Could this be added for custom services as well?

Category: Data Management

J

We need this for OData service calls too!

Category: Data Management

J

I agree with with Mehrdad and John on the security concerns. If you have access to the staging table, you should be able to look at the raw data.

Not having this makes troubleshooting very difficult. We need it badly. Right now, the only way is to ask someone on the other end of the integration for the "File". Depending on the integration technology, they may not have a copy of exactly what they put on the wire in the http post.

We're burning days in implementation projects resolving these issues.

Please consider adding this functionality. Or at least give us the option to implement it via an extension (just give us a way to get a download link).

Category: Data Management

J

Related to the data protection, it should be possible to allow or not the access to the incoming file content on the data project level. It should also be protected by the role based security. People who has access to the staging data should also be able to have a look into the file content.

But aside the data protection discussion, being able to keep and access data from the execution history is a very powerful tool for data debugging (especially in cases where the data event not get imported in the staging tables) .

It is not only for the operation/live scenarios important to have this visibility and traceability but also for the project implementation and data migration phase for obvious reasons that during these phases the chance to end-up in this kind of scenarios is much higher.

Category: Data Management

J

Sunil,


Sorry for the delay in getting back to you.  This came up on one our weekly implementation calls with MSFT, so I just popped in to check the status and saw your note.


I've reviewed your security concern with a few key individuals on the implementation team and we're all of the mindset that if someone has access to the staging table, why not give them access to the file as well.  Only a poorly designed integration would contain extra pieces of information that are not imported, let alone sensitive pieces of information.  Also, my experience with inbound DMF integration is such that the file needs to include all elements contained in the mapping.  Whenever we exclude fields or add extra fields not contained in the DMF mapping, it fails.  


So our position is that for well designed integrations, there should be no additional security concern if you provide access to the file.

Category: Data Management

J

Hi John-- thanks for sharing this idea.


Agree that this will be quite useful in debugging. Now, one concern would be that having this capability will then make sensitive data available to users that may not otherwise have access to. Having access to the staging table is one thing but getting access to an entire file make me nervous about this ask!


Of course one should be able to secure this feature via role based security but, the bigger concern is the easy access to an entire file of sensitive data/transactions.


Thoughts on this?

Category: Data Management

J

There is an option to submit a DMF job when using the "Load project" option, but that requires going through many steps to do so, and can possibly corrupt the project. It would be nice that when you select "Run project" to just attach a different file and run as defined, that you can submit to batch that way.

Category: Data Management