We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
The default delimited log file definitions are quite restrictive and limit what we can do when importing more complex log files and information. The Message Tracking Logs from Exchange overruns the available options for Fields quite quickly and there are many places where we would want to use lookup text, far grater than the default of 8. There are more text fields in that log file than there are available text inputs, in particular for length of strings.
Additionally there are some logs and other sources of information where we would need to add groupings and support for nested data. The Exchange tracking logs have a few places where data is sub divided beyond the comma with a semi colon to break down even more data (recipients etc). Another area where this would be useful is importing from PowerShell and being able to absorb objects and columnize/nest the data.
0 Votes
0 Comments
Login or Sign up to post a comment