29

Data management entity's exports empty files i.e. if no data to export still it exports a blank file.


Problem statement: Assume 30 interfaces (Per legal entity) scheduled to export every minute, which will result in huge export history per hour. i.e. (30 * No of legal entity * 60 minutes) Manually finding 1 execution where exactly the data is exported in next to impossible, space usage on blob and for integrating application like BizTalk directly consuming these messages using Dequeue involves execution cost.


As mentioned above this has issue at two levels especially for Recurring jobs.



  • In the recurring data jobs execution history it is impossible to find the execution with data is next to impossible.

  • Integrating application like BizTalk directly consuming these messages using Dequeue involves execution cost.


Potential solution/design: Having a condition to check if records/record count is greater than 0 will restrict the exporting of empty files. This condition should be controlled by the user. Ex: Like skip staging option on data project there should be another parameter to allow user to choose export a file only if it has data. This way it will be more flexible and suitable for any customer scenarios. This resolution at the core level of API’s will control the flow of the messages with minimal change and simple design to address the above problems.

Category: Data Management
STATUS DETAILS
Completed
Ideas Administrator

Thanks for sharing the feedback and pushing for this one. We have completed this work and the feature will be in PU12.

 

 

Comments

H

This is very basic and mandatory requirement. voted UP and would love to be part of next release !!

Category: Data Management

H

This is a must have and proposed design and solution is suitable. I would love to see this developed and be available as a hotfix ahead of next release, since currently running projects badly need this solution. We cannot wait till 2017 Autumn Release.

Category: Data Management

H

Blank files are generated each time the batch job runs. It is almost impossible to find out the file with data if the batch job is set to run every min or even 5 mins. This issue must be resolved inorder to save time searching for the file with data and also to reduce the performance load it takes just to generate blank files.

Category: Data Management

H

It is more than logic for any ERP system to be able to run jobs periodically and, in case of no outcome, to suppress any further processing.


Itis a best practice that will sustain AX365 's ambition to become one of world's best ERP's.


The advantages of this approach have already been explained by Hari, and I endorse them fully.


 


Ignace

Category: Data Management