|Inquiries within a module in AX|
I have often wondered myself what an Inquiry in AX was and how they came to be. Over time, I am understanding this concept a little better, so this blog post is my grasp at what an Inquiry is in AX based on my observations.
So, what is an Inquiry?
|Job list Inquiry in the Production control module|
The actual word inquiry means "an act of asking for information" with the synonyms of query and question. It only makes sense that an Inquiry in AX would help an end user solve a problem that they are having or present an answer to their burning questions in a readable format.
Reports vs. Inquiries in AX
Some people are of the thought that Reports and Inquiries in AX are basically the same thing. They are not.
A Report in AX is static. When you run a Report, you get a snapshot of data that can be printed and laid on someone's desk. True, you can save the report to Excel and manipulate the data there, but ultimately, a Report is a tool used to give a static snapshot into your data using defined parameters.
An Inquiry in AX is dynamic. Inquiries take your data and present it to the users in a new way. Sometimes they are set to be viewed only, but often they provide users a new way to see and easily manipulate their data. This is something that cannot be done in a report as it is presented in AX.
What are your thoughts? How would you describe an Inquiry in AX?